-
1. Re: Example of jboss-esb.xml with JCA provider
kconner Mar 19, 2008 12:57 PM (in response to lafbarbosa)You do not need to do anything with these attributes unless you are overriding the current JCA configuration. The jms-jca-provider already provides default values for these.
-
2. Re: Example of jboss-esb.xml with JCA provider
lafbarbosa Mar 19, 2008 1:22 PM (in response to lafbarbosa)Hi Kevin,
Ok, but if I don't use these attributes related above, which is the difference between use a jms-provider and a jms-jca-provider? Because it seems to be exactly the same.
For example:
<jms-provider name="CallbackQueue-JMS-Provider" connection-factory="ConnectionFactory">
<jms-bus busid="jBPMCallbackBus">
<jms-message-filter dest-type="QUEUE" dest-name="queue/CallbackQueue"/>
</jms-bus>
</jms-provider>
<jms-jca-provider name="CallbackQueue-JMS-Provider" connection-factory="ConnectionFactory">
<jms-bus busid="jBPMCallbackBus">
<jms-message-filter dest-type="QUEUE" dest-name="queue/CallbackQueue"/>
</jms-bus>
</jms-jca-provider>
Could you give me some idea about the usage of each one?
Thanks in advance!
Regards,
Luiz -
3. Re: Example of jboss-esb.xml with JCA provider
kconner Mar 20, 2008 5:48 AM (in response to lafbarbosa)The similarity in the configuration is intentional.
The jca-jms-provider uses JCA to deliver the JMS messages into the ESB and can therefore take advantage of encompassing transactions, the jms-provider uses the normal JMS connections and is not transactional.
You should be able to change a jms-provider into a jca-jms-provider is you wish to use a transactional context.