[jboss-dev-forums] [Design of JCA on JBoss] - Re: JBPAPP-750 - Integration between AS and JBossMessaging 1

[adrian@jboss.org]

"jesper.pedersen" wrote : I'm currently looking at
  | 
  |  http://jira.jboss.com/jira/browse/JBPAPP-750
  | 
  | with the integration between the EAP and JBossMessaging since JBM implements both the non-XA and XA interfaces. XA mode is selected at session level.
  | 
  | 1)
  | Is the best way to handle this to extend the JmsConnectionRequestInfo class 
  | with XA information - f.ex. UseXA - and then use this information when 
  | creating the sessions in JmsManagedConnection::setup() ?
  | 
  | Of course there will be other changes also JmsMCFProperties, ... Creating 
  | f.ex. a JmsXASession class may be an idea.
  | 

No. XA or local is a property of the connection factory deployment not the request.

anonymous wrote : 
  | 2)
  | JmsActivation also need information about XA from JmsActivationSpec in order to create the correct connection type - so UseXA here.
  | 
  | Any feedback on how this should be done is most welcome

If you can't determine the type from the real ConnectionFactory 
then there's no portable way for you to determine what
type of jca deployment you are in. The current jms resource adapter
assumes the connection factory in the jms provider is consistent with the
connection manager choice.

This is just a testsuite issue (the idea is to test local only jms connection usage).

A simple fix (in the testsuite) would be to create a wrapper connection factory that 
* only implements the non xa interfaces 
* delegates to the real connection factory
* bind it into jndi with a different name
* create a LocalJMSProvider using that wrapper for the test

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

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