Hi Ant, I suppose this is going to simply use the StAX processor that we currently have for jms binding. That being the case I see there is going to be circular dependency issues
If this is sorted out, I guess then the definitions processor will just about be able to read this instance of binding.jms and add it to the model resolver. Then the binding instance that is referring to this in the composite should resolve this with the model resolver. Thanks - Venkat On Sat, Mar 8, 2008 at 4:32 PM, ant elder <[EMAIL PROTECTED]> wrote: > I'd like to add support for the request/response Connection attributes of > the JMS binding (see lines 119 and 123 of the JMS binding spec) and > wondered > if the existing code in the policy framework would be able to support this > today or if I'd need to extend it with some new SPI or something? > > These attributes enable defining jms binding configurations in a > definitions.xml file and referring to those from the binding in a > composite, > eg: > > <composite> > <service> > <binding.jms requestConnection="StockQuoteService" /> > </service> > . . . > </composite> > > and > > <definitions> > <binding.jms name="StockQuoteService" > initialContextFactory=" > org.apache.activemq.jndi.ActiveMQInitialContextFactory" > jndiURL="tcp://localhost:61616"> > <destination name="StockQuoteServiceQueue" create="never"/> > <connectionFactory name="StockQuoteServiceQCF" create="never"/> > </binding.jms> > </definitions> > > Does anyone who know the policy code have any comments, suggestions or > hints? > > ...ant >
