[jboss-jira] [JBoss JIRA] (WFLY-2936) "Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction" error in migrated seam 2.2.2 application

Eduardo Martins (JIRA) issues at jboss.org
Fri Feb 21 04:47:47 EST 2014


    [ https://issues.jboss.org/browse/WFLY-2936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12946752#comment-12946752 ] 

Eduardo Martins commented on WFLY-2936:
---------------------------------------

Hi Dimitris, that ear is referring (missing) modules that override the ones bundled with WFLY, and it is also bundling a lot of stuff in the ear lib that is already present in bundled modules, can you clean that share such ear, and in case there are source changes reattach these too? Otherwise it's quite hard for me to ensure there is an issue in WFLY with standard Java EE apps, and fix it for next minor release, our main priority right now.
                
> "Only session and message-driven beans with bean-managed transaction demarcation are allowed to access UserTransaction" error in migrated seam 2.2.2 application
> ----------------------------------------------------------------------------------------------------------------------------------------------------------------
>
>                 Key: WFLY-2936
>                 URL: https://issues.jboss.org/browse/WFLY-2936
>             Project: WildFly
>          Issue Type: Feature Request
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 8.0.0.Final
>         Environment: Windows 7 64bit
> Java 1.7.0_51
> WildFly 8.0.0.Final
> JBoss Seam 2.2.2.Final
>            Reporter: Dimitris Keramidas
>         Attachments: Auth.java, Authenticator.java, components.xml, jboss-deployment-structure.xml, server.log
>
>
> The error is fired when attempting to call a transaction-enabled EJB method, from a seam component. Specifically the authentication component.
> In order to get to this position, the project's deployment descriptors had to be migrated. Furthermore, mojarra version 1.2_15 was deployed to WildFly, as described by this link: https://community.jboss.org/wiki/DesignOfWildFlyMulti-JSFFeature
> Please see attached logs and descriptors.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira


More information about the jboss-jira mailing list