Hi, We are trying to use a JMS binding component within ServiceMix and have come up with a tricky issue..We were told that the <jms:consumer> binding component was better than a <jms:endpoint> binding component in terms of memory usage etc...<jms:consumer> component take in concurrentConsumers and cacheLevel attributes and they give it a huge performance boost. But, the problem with using <jms:consumer> is that we cannot give it a defaultMep and defaultOperation attributes that are necessary if an Apache ODE engine is used as the next point of communication. Is there any way we can add 1) concurrentConsumers, cacheLevel attributes to a <jms:endpoint> OR 2) defaultMep, defaultOperation attributes to a <jms:endpoint>
I am looking at non-programmatic ways of doing the same. We figured out how to do it programmatically ...but that would be tweaking with binding component code which I am not highly in favor of.. Really wonder why we should have <jms:endpoint>, <jms:consumer> to do jms operations? Why can't it all the options just be available for <jms:endpoint>....am i missing something? Thanks for your help. -- View this message in context: http://www.nabble.com/jms%3Aendpoint%2C-jms%3Aconsumer-tf4250483s12049.html#a12097098 Sent from the ServiceMix - User mailing list archive at Nabble.com.
