[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

[Ben Software Engineer (JIRA)]

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

Ben Software Engineer commented on WFLY-2936:
---------------------------------------------

Hi Eduardo - thanks for the thoughts and comments.  We are also in the middle of a Seam 2.1 Jboss 5 upgrade to Seam 2.3 and (hopefully) wildfly.  This appears to not be an issue with JBoss 7.1.1.final, but I realize wildfly has evolved from that on many fronts.  This is a major blocker for anyone trying to use Seam I think and would be nice if some alternative config can be set in wildfly module to allow this, perhaps registering the calling class only or some means of limiting who can bypass this security check.  Can you explain as to what specifically the security check is about?  Also can someone open up a JIRA on seam side, as I do not seen this critical blocker listed here:
https://issues.jboss.org/browse/JBSEAM/fixforversion/12321763

Thank you.
                
> "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
>            Assignee: Eduardo Martins
>         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