Calling getCallerPrincipal should not be permitted on lifecycle methods - on @PreDestroy is allowed
---------------------------------------------------------------------------------------------------
Key: AS7-2853
URL: https://issues.jboss.org/browse/AS7-2853
Project: Application Server 7
Issue Type: Bug
Reporter: Ondřej Chaloupka
Assignee: Stuart Douglas
Calling method on getCallerPrincipal should cause throwing IllegalStateException (EJB3.1 17.2.5) on lifecycle methods @PostConstruct, @PreDestroy but it returns anonymous identity role on @PreDestroy annotated method.
Test could be found:
https://github.com/ochaloup/jboss-as/blob/JBQA-5451-test-migration-getcal...
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
EJBContext.isCallerInRole and EJBContext.getCallerPrincipal do not throw IllegalStateException when not allowed
---------------------------------------------------------------------------------------------------------------
Key: AS7-1064
URL: https://issues.jboss.org/browse/AS7-1064
Project: Application Server 7
Issue Type: Bug
Components: EJB
Affects Versions: 7.0.0.CR1
Reporter: Carlo de Wolf
Priority: Critical
Fix For: 7.1.0.CR1
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
Reference between ejb2 and ejb3 beans failing
---------------------------------------------
Key: AS7-3021
URL: https://issues.jboss.org/browse/AS7-3021
Project: Application Server 7
Issue Type: Bug
Reporter: Ondřej Chaloupka
Assignee: John Bailey
The way how it was possible to reference EJB2 beans in EJB3 beans does not work. The migration of test from AS5 could be check on (2 jars in an ear file):
https://github.com/ochaloup/jboss-as/tree/JBQA-5483-test-migration-ejb2re...
There is 2 problems currently:
- to use EJB2 bean from EJB3 has problem in case that ejb-jar.xml (for EJB3 bean) does not specify <remote> interface (deploy fails)
- @EJB annotation not bound ejb2 bean via mappedName (see the test example)
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira