[jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-4263) Incorrect transaction attribute specified on an EJB implementing the SessionSynchronization interface

Alexandrina Ivanova (JIRA) jira-events at lists.jboss.org
Wed Jun 24 12:32:56 EDT 2009


     [ https://jira.jboss.org/jira/browse/JBSEAM-4263?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Alexandrina Ivanova updated JBSEAM-4263:
----------------------------------------

    Description: 
Hello Seam Team,

An incorrect transaction attribute SUPPORTS is specified on bean org.jboss.seam.transaction.EjbSynchronizations, located in jboss-seam.jar. The bean EjbSynchronizations implements the SessionSynchronization interface but according to the EJB 3.0 specification the allowed transaction attributes for its methods are: REQUIRED, REQUIRES_NEW, MANDATORY.

JSR 220: Enterprise JavaBeansTM,Version 3.0
EJB Core Contracts and Requirements
Chapter 13.3.7 Specification of the Transaction Attributes for a Bean's Methods
"If an enterprise bean implements the javax.ejb.SessionSynchronization interface, only the
following values may be used for the transaction attributes of the bean's methods: REQUIRED,
REQUIRES_NEW, MANDATORY.
The above restriction is necessary to ensure that the enterprise bean is invoked only in a transaction. If
the bean were invoked without a transaction, the container would not be able to send the transaction
synchronization calls."

Proposal for fix: change the transaction attribute of the EjbSynchronizations bean from SUPPORTS to REQUIRED.

Best regards,
Alexandrina

  was:
Hello Seam Team,

An incorrect transaction attribute SUPPORTS is specified on bean org.jboss.seam.transaction.EjbSynchronizations, located in jboss-seam.jar. The bean EjbSynchronizations implements the SessionSynchronization interface but according to the EJB 3.0 specification the allowed transaction attributes for its methods are: REQUIRED, REQUIRES_NEW, MANDATORY.

JSR 220: Enterprise JavaBeansTM,Version 3.0
EJB Core Contracts and Requirements
Chapter 13.3.7 Specification of the Transaction Attributes for a Bean's Methods
"If an enterprise bean implements the javax.ejb.SessionSynchronization interface, only the
following values may be used for the transaction attributes of the bean's methods: REQUIRED,
REQUIRES_NEW, MANDATORY.
The above restriction is necessary to ensure that the enterprise bean is invoked only in a transaction. If
the bean were invoked without a transaction, the container would not be able to send the transaction
synchronization calls."

Proposal for fix: change the transaction attribute of the EjbSynchronizations from SUPPORTS to REQUIRED.

Best regards,
Alexandrina

       Priority: Major  (was: Minor)


> Incorrect transaction attribute specified on an EJB implementing the SessionSynchronization interface
> -----------------------------------------------------------------------------------------------------
>
>                 Key: JBSEAM-4263
>                 URL: https://jira.jboss.org/jira/browse/JBSEAM-4263
>             Project: Seam
>          Issue Type: Bug
>          Components: EJB3
>    Affects Versions: 2.1.2.GA
>            Reporter: Alexandrina Ivanova
>
> Hello Seam Team,
> An incorrect transaction attribute SUPPORTS is specified on bean org.jboss.seam.transaction.EjbSynchronizations, located in jboss-seam.jar. The bean EjbSynchronizations implements the SessionSynchronization interface but according to the EJB 3.0 specification the allowed transaction attributes for its methods are: REQUIRED, REQUIRES_NEW, MANDATORY.
> JSR 220: Enterprise JavaBeansTM,Version 3.0
> EJB Core Contracts and Requirements
> Chapter 13.3.7 Specification of the Transaction Attributes for a Bean's Methods
> "If an enterprise bean implements the javax.ejb.SessionSynchronization interface, only the
> following values may be used for the transaction attributes of the bean's methods: REQUIRED,
> REQUIRES_NEW, MANDATORY.
> The above restriction is necessary to ensure that the enterprise bean is invoked only in a transaction. If
> the bean were invoked without a transaction, the container would not be able to send the transaction
> synchronization calls."
> Proposal for fix: change the transaction attribute of the EjbSynchronizations bean from SUPPORTS to REQUIRED.
> Best regards,
> Alexandrina

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

        



More information about the seam-issues mailing list