On Saturday 11 October 2008 3:34:52 am Christian Schneider wrote: > Hi Dan, > > sounds reasonable to me. I have added the config element to address and > set the default.
I think setting useJms11 to false for 2.0.x and 2.1.x probably makes sense for compatibility sake. For 2.2 (trunk), it probably make sense to set the default to true. If the provider is 1.1 capable, we probably should use it, but provide the option for the user to downgrade to 1.0.2 if they need it. Dan > > Greetings > > Christian > > Daniel Kulp schrieb: > > Christian, > > > > The old JMS transport pretty much just used the JMS 1.0.2 API's so it > > worked with old versions of JMS providers and such. The new stuff seems > > to default to 1.1 which is causing issues. I see that if you use the > > new config, it's settable. However, if you use the old wsdl based > > stuff, it cannot. I'm wondering if it make sense for the line in > > JMSOldConfigHolder that reads: jmsConfig.setUseJms11(true); > > should be changed to false to be compatible with the old version? > > > > I suppose we could add a optional "useJms11" attribute (default to false) > > on one of the old extensors (address maybe?) to set this so if someone > > wants to use 1.1, they could, but default behavior is maintained. > > > > Thoughts? -- Daniel Kulp [EMAIL PROTECTED] http://dankulp.com/blog
