[jboss-dev-forums] [Design of Messaging on JBoss (Messaging/JBoss)] - Re: Bug in transactional delivery in an MDB

[weston.price@jboss.com]

anonymous wrote : 
  | But it is not what we want all cases 
  | 

Then you wouldn't use JCA. Keep in mind there is nothing to prevent you from using JMS without the JCA integration if you don't want pooling and automatic transaction enlistment. You can always use the non JCA CF from JNDI. The JCA resource adapter is designed to provide transactional support to Servlet and EJB appliation components in transparent manner in the same vein as JDBC resources (also JCA).

anonymous wrote : 
  | Sounds like the design is broken. You are forcing us to always be always used as XA, because you use instanceof to tell the XAConnectionFactory and ConnectionFactory apart. 
  | 

The JMS/JCA adapter is an XA  resource adapter, it's purpose is to support a JMS provider as a transactional resource. In the case that the JMS provider is not XA capable (not desired) then we use the local JMS API to achieve the same results via an XA compliant wrapper and the LRCG. The local API is a fallback in the case that that the provider does not support XA. 

I would be surpised is any of this is effecting the testsuite/TCK. But again, without a stack trace or any other information I can't say for sure. 















View the original post : http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4040165#4040165

Reply to the post : http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&p=4040165