[weld-issues] [JBoss JIRA] Commented: (CDITCK-75) @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest

[Pete Muir (JIRA)]

    [ https://jira.jboss.org/jira/browse/CDITCK-75?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12496083#action_12496083 ] 

Pete Muir commented on CDITCK-75:
---------------------------------

Please exclude them.

> @RunAs role in org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest
> -------------------------------------------------------------------------------------------------
>
>                 Key: CDITCK-75
>                 URL: https://jira.jboss.org/jira/browse/CDITCK-75
>             Project: CDI TCK
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) 
>    Affects Versions: 1.0.0.GA
>         Environment: X86/Ubuntu
>            Reporter: Hong Zhang
>            Assignee: David Allen
>             Fix For: 1.0.1.CR1
>
>
> org.jboss.jsr299.tck.tests.event.observer.transactional.TransactionalObserversTest failed to deploy on glassfish server due to no security role mapping for @RunAs roles defined in EJB classes.  By creating a default mapping in glassfish through sun-ejb-jar.xml, the test was able to deploy/run. But we were wondering about the intention of the @RunAs role as the tests do not seem to actually use the security constraints.
> And when this test ran in JBoss environment, how is the security role mapping done for these @RunAs roles? 

-- 
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