[jboss-jira] [JBoss JIRA] Moved: (EJBTHREE-2263) @SecurityDomain doesn't work with @Singleton
[
https://issues.jboss.org/browse/EJBTHREE-2263?page=com.atlassian.jira.plu...
]
jaikiran pai moved JBAS-9244 to EJBTHREE-2263:
----------------------------------------------
Project: EJB 3.0 (was: Legacy JBoss Application Server 6 )
Key: EJBTHREE-2263 (was: JBAS-9244)
Affects Version/s: depchain-1.0.1
depchain-1.0.0
(was: 6.0.0.Final)
Component Fix Version(s): jboss-ejb3-singleton:1.0.1
Component/s: Security
singleton
(was: Security)
(was: EJB)
Security: (was: Public)
Fix Version/s: depchain-1.0.2
(was: 6.1.0)
@SecurityDomain doesn't work with @Singleton
--------------------------------------------
Key: EJBTHREE-2263
URL: https://issues.jboss.org/browse/EJBTHREE-2263
Project: EJB 3.0
Issue Type: Bug
Components: Security, singleton
Affects Versions: depchain-1.0.1, depchain-1.0.0
Environment: Windows Vista, java version "1.6.0_23"
Reporter: Christian Reiter
Assignee: jaikiran pai
Labels: security_domain, singleton
Fix For: depchain-1.0.2
Attachments: login-config.zip, SingletonAuthTest_Client.zip,
SingletonAuthTest_EE_App.zip, SingletonAuthTest_Interfaces.zip
In Jboss AS 6 (6.0.0.Final) the Annotation @SecurityDomain from the package
org.jboss.ejb3.annotation.SecurityDomain doesn't seem to work with @Singleton -
SessionBeans.
If I try to call a method from a @Singleton which is marked with @RolesAllowed i get a
"java.lang.IllegalStateException: Security Context has not been set" Exception.
If I do completely the same with a @Stateless SessionBean everything works fine.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira