[jboss-dev-forums] [Design of JCA on JBoss] - Re: Problems JCA JMS inflow issue and tx NotSupported

[weston.price@jboss.com]

The *easiest* thing to do would be to patch 4.0.5 and then make this patch available in the next cummulative patch release. The changes that made it in to 4.0.5 should simply be replaced with the new stuff. This will be the case with 4.2. Again, this is why I never wanted this backport to happen. 

anonymous wrote : 
  | I'm not trying to attribute blame, just trying to work out what is going on, and find a solution. :)
  | 

Your altruism is quite refreshing. 

anonymous wrote : 
  | If you are saying that the 4.0.5.GA code is a bodged backport and basically doesn't work, and there's no chance of getting it fixed, then we can tell our customers not to use that and stick with the JMSContainerInvoker until JB5.
  | 

That is not what I am saying. I am more that willing to address any issues you think might be occuring with JCA and JBM. Again, a patch release in our cummulative QA patch cycle is most likely the best approach. 

anonymous wrote : 
  | (What about AS4.2 - I would have thought we would want the good HEAD version in that?)
  | 

Yes, the code in HEAD will be in 4.2. 

anonymous wrote : 
  | For JBM1.2, we need to make sure that all these cases work, so I am going to improve the MDB integration tests and make sure they run with both the JMSContainerInvoker and JCA1.5 inflow. 
  | 

Yes, this is simply a matter of running the testsuite against HEAD really where JBM is the default. Unfortunately, I haven't paid much attention to this as most of us are working on getting the TCK issues resolved and finalized. 

anonymous wrote : 
  | Right now the MDB test coverage is scrappy (no blame) to say the least which is why issues like this and others are slipping through the net. 
  | 

Not really. There is a decent framework for testing both the JCA adapter and the container invoker. Again, I think this is simply a matter of dealing with JBM which up until recently I was aware had any issues. Since this is the first time I am hearing about this and 4.0.5 has been in the wild for a bit (at least enough time to accumulate a patch release), I am assuming that we are simply running into some scenarios with JCA/JBM that have not been accounted for at this point. 









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

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