> > If you don't mind helping debug it (which would be awesome BTW!), I > guess you could set a breakpoint in the > JmsConfiguration.createMessageListenerContainer() and see what > MessageListenerContainer is created by Camel and how its configured - > to see if there's any real difference at all in how Camel configures > it to how you've configured it explicitly? That must be the problem I > guess?
Well, the container returned from JmsConfiguration.createMessageListenerContainer() seems to be the default one. That explains why it works in non-ax with jmstransactionmanager, since the default is autoack, right? It seems as if I am missing something fundamental here? I feel the smell of a new user rtfm problem, but where is it? :) How is my JmsComponent looked up by camel? Right now it's just registered in the spring application context, I was assuming that you had some beanprocessor looking for components, and registering them with camel? -- /Magnus Heino
