[jboss-jira] [JBoss JIRA] Resolved: (JBAS-3321) Support for "method-attributes" including "transaction-timeout" for MDBs

[Weston Price (JIRA)]

     [ http://jira.jboss.com/jira/browse/JBAS-3321?page=all ]

Weston Price resolved JBAS-3321.
--------------------------------

    Fix Version/s: JBossAS-4.2.0.CR1
       Resolution: Done

Added transaction timeout to org.jboss.resource.adapter.jms.inflow.JmsActivationSpec and associated code to set the transaction timeout in XATransactionDemarcationStrategy on the TM prior to XAResource being enlisted in the global transaction.

> Support for "method-attributes" including "transaction-timeout" for MDBs
> ------------------------------------------------------------------------
>
>                 Key: JBAS-3321
>                 URL: http://jira.jboss.com/jira/browse/JBAS-3321
>             Project: JBoss Application Server
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>          Components: EJB2
>    Affects Versions: JBossAS-4.0.4.GA
>            Reporter: Galder Zamarreno
>         Assigned To: Weston Price
>             Fix For: JBossAS-4.2.0.CR1
>
>
> Looking at jboss_4_0.dtd it seems that MDBs in JBoss do not support the use of "method-attributes", 
> particularly "transaction-timeout", why is this?
> I have looked in to this a little and it doesn't seem to be prohibited by the J2EE specs, in fact 
> Weblogic seems to support the setting of transaction timeouts on MDBs, so why not JBoss?
> I guess it is either an error or a deliberate design decision not to support it, if it's the latter I 
> would be interested to hear what the rational is?
> Adrian Brock wrote:
> Because the MDB transaction is not started by the EJB container
> like the other EJB types.
> Raise a feature request. There is no reason why the ServerSessionPool
> cannot ask the EJB container for this information. 
> _________________
> Adrian Brock
> Chief Scientist
> JBoss, Inc.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira