JBAS-3321 -- Method attributes and transaction timeout

[weston.price]

If the EJB3 implementation can pass me this information, I can go ahead and do this. It's pretty straightforward now that the new transaction enlistment stuff is more clear and has been put into place. Simplest solution would be to include it in the JmsActivationSpec as a override to the default transaction timeout.

[bill.burke]

why does the adapter need to handle this? Can't this be done in an EJB interceptor like it is already done?

[weston.price]

This is for MDB's where I begin the transaction and enlist the provider (ie inflow) To my knowledge you guys don't set those and even if you did, I don't believe it would have any effect because it has to be set prior to beginning the transaction.

[bill.burke]

TM.setTransactionTimeout needs to happen *before* the transaction is started?

[bill.burke]

BTW, wouldn't this need to be done as an ActivationConfigSpec to keep the RAR portable? EIther that or we're gonna have to hack it in through a ThreadLocal variable.

[weston.price]

According to the API:

"public void setTransactionTimeout(int seconds)
throws SystemException

Modify the timeout value that is associated with transactions started by subsequent invocations of the begin method. If an application has not called this method, the transaction service uses some default value for the transaction timeout."

Again, this is just for inflow so you are talking about a completely new thread with no transaction context.

[weston.price]

Right ActivationSpecConfig would be the only way to go.