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

Hong Zhang (JIRA) jira-events at lists.jboss.org
Mon Nov 23 10:00:29 EST 2009


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

Hong Zhang commented on CDITCK-75:
----------------------------------

Thanks for looking at the issue so quickly!
To clarify: will revision 5112 be in the next snapshot drop of the TCK we get to run against v3 or revision 5112 only be included in next TCK release which will run against the next version of the v3 (v3.1)?
I just want to know if we exclude these tests now with the current version of the TCK, do we need to re-surrect them when the next TCK drop comes for v3? If yes, we would like to get hold of the new tests soon so we know for sure the new version of the tests deploy/run ok with the glassfish v3.  If it's only for next release (v3.1), we will be all set for v3 after excluding 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

        


More information about the weld-issues mailing list