[jboss-dev-forums] [Design of JCA on JBoss] - Re: JBAS-3321 - TransactionTimeout from EJB container

[weston.price@jboss.com]

anonymous wrote : 
  | The vast majority of inflow rars don't do this. With the exception of transaction inflow
  | there is no way for them to start a transaction, there's no spec defined integration
  | point to get the transaction manager. 
  | 

Correct. I I hope to remedy this in JCA (1.6) ;-)

anonymous wrote : 
  | They leave it to the container (message endpoint) to start the transaction from the ejb metadata. What they do is pass the XAResource to the MessageEndpoint
  | so they can take part in the transaction.
  | i.e. the XAResource is automatically enlisted in the transaction when the
  | beforeDelivery or "deliver" starts the transaction. 
  | 

Also, correct. Unfortunately, there are some JMS providers (that shall remain nameless) that will not work in this manner. So, we also have to have some way to allow for the timeout prior to the actual delivery of the message.  This can easily be remedied with AOP which is probably the *right* way to do this anyway.

anonymous wrote : 
  | If we start the transaction, we should apply the configuration from jboss.xml
  | or the relevant ejb3 annotation. 
  | 

This is what's in place now via the ActivationSpec. This was the point of the  *fix*. You are simply proposing moving it to the MEF. I don't necessarily disagree with this I am simply wondering why. 

The 'it's not generic' answer doesn't fly with me because the MEF solution isn't necessarily generic either. It's simply another way to achieve the same thing with the benefit that it can be leveraged by all inbound RARS that we write which has some merit, I agree. 



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

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