[jboss-jira] [JBoss JIRA] Resolved: (EJBTHREE-1945) RunAsIdentity is not propagated correctly

[Carlo de Wolf (JIRA)]

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

Carlo de Wolf resolved EJBTHREE-1945.
-------------------------------------

    Fix Version/s: bom-as6-0.2.0
       Resolution: Cannot Reproduce Bug


test-with-jvmargs:
   [delete] Deleting: /home/carlo/work/jbossas/projects/ejb3/trunk/testsuite/target/log/test.log
    [junit] Running org.jboss.ejb3.test.ejbthree1945.unit.RunAsPrincipalTestCase
    [junit] Tests run: 4, Failures: 0, Errors: 0, Time elapsed: 1.687 sec

> RunAsIdentity is not propagated correctly
> -----------------------------------------
>
>                 Key: EJBTHREE-1945
>                 URL: https://jira.jboss.org/browse/EJBTHREE-1945
>             Project: EJB 3.0
>          Issue Type: Bug
>          Components: core
>    Affects Versions: Plugin 1.0.17
>            Reporter: Anton Kolmakov
>            Assignee: Carlo de Wolf
>             Fix For: bom-as6-0.2.0
>
>
> I have one message driven bean  A and two stateless beans B and C.
> A annotated with @RunAs, @RunAsPrincipal and @SecurityDomain.
> B and C annotated with @SecurityDomain.
> A receives message and calls B which calls C.
> RunAsIdentity is propagated to B only but not to C. 
> Why? Is it expected behavior? 
> I expect propagation of RunAsIdentity to all beans in execution chain after bean with @RunAs* annotations.

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