[JBoss JIRA] Created: (JBMETA-56) Handle ejb local refs within message-driven declarations for EJB2.1
11:07 p.m.
Handle ejb local refs within message-driven declarations for EJB2.1
-------------------------------------------------------------------
Key: JBMETA-56
URL: http://jira.jboss.com/jira/browse/JBMETA-56
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public (Everyone can see)
Affects Versions: 1.0.0.Beta20, 1.0.0.Beta19
Reporter: Anil Saldhana
Assigned To: Emanuel Muckenhuber
Consider a ejb-jar.xml snippet:
=========================
<message-driven>
<description>An mdb that access an entity bean as InternalUser to
test propagation of the run-as role through several levels</description>
<ejb-name>DeepRunAsMDB</ejb-name>
<ejb-class>org.jboss.test.security.ejb.RunAsPropagationMDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
<ejb-local-ref>
<ejb-ref-name>ejb/CalledSessionLocalHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>org.jboss.test.security.interfaces.CalledSessionLocalHome</local-home>
<local>org.jboss.test.security.interfaces.CalledSessionLocal</local>
<ejb-link>Level1MDBCallerBean</ejb-link>
</ejb-local-ref>
<security-identity>
<description>Use a role that is not assigned to any users to
access restricted server side functionallity</description>
<run-as>
<role-name>InternalRole</role-name>
</run-as>
</security-identity>
<resource-ref>
<description>Default QueueFactory</description>
<res-ref-name>jms/QueFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>
=========================
Now something for JBossEnterpriseBeanMetaData (Environment env =
bean.getJndiEnvironmentRefsGroup()) should contain the ejb-local refs.
I think the tests need to be updated to handle this case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:11 p.m.
New subject: [JBoss JIRA] Commented: (JBMETA-56) Handle ejb local refs within message-driven declarations for EJB2.1
[ http://jira.jboss.com/jira/browse/JBMETA-56?page=comments#action_12416606 ]
Anil Saldhana commented on JBMETA-56:
-------------------------------------
At the moment, in AS5 testsuite,
org.jboss.test.security.test.EJBSpecUnitTestCase.testMDBRunAs etc are failing with a
lookup of java:comp/env/ejb/xxxx in the MDBs because the ejb local refs have not been set
properly.
Handle ejb local refs within message-driven declarations for EJB2.1
-------------------------------------------------------------------
Key: JBMETA-56
URL: http://jira.jboss.com/jira/browse/JBMETA-56
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.Beta19, 1.0.0.Beta20
Reporter: Anil Saldhana
Assigned To: Emanuel Muckenhuber
Consider a ejb-jar.xml snippet:
=========================
<message-driven>
<description>An mdb that access an entity bean as InternalUser to
test propagation of the run-as role through several levels</description>
<ejb-name>DeepRunAsMDB</ejb-name>
<ejb-class>org.jboss.test.security.ejb.RunAsPropagationMDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
<ejb-local-ref>
<ejb-ref-name>ejb/CalledSessionLocalHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>org.jboss.test.security.interfaces.CalledSessionLocalHome</local-home>
<local>org.jboss.test.security.interfaces.CalledSessionLocal</local>
<ejb-link>Level1MDBCallerBean</ejb-link>
</ejb-local-ref>
<security-identity>
<description>Use a role that is not assigned to any users to
access restricted server side functionallity</description>
<run-as>
<role-name>InternalRole</role-name>
</run-as>
</security-identity>
<resource-ref>
<description>Default QueueFactory</description>
<res-ref-name>jms/QueFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>
=========================
Now something for JBossEnterpriseBeanMetaData (Environment env =
bean.getJndiEnvironmentRefsGroup()) should contain the ejb-local refs.
I think the tests need to be updated to handle this case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:54 p.m.
New subject: [JBoss JIRA] Resolved: (JBMETA-56) Handle ejb local refs within message-driven declarations for EJB2.1
[ http://jira.jboss.com/jira/browse/JBMETA-56?page=all ]
Emanuel Muckenhuber resolved JBMETA-56.
---------------------------------------
Fix Version/s: 1.0.0.CR1
Resolution: Done
Handle ejb local refs within message-driven declarations for EJB2.1
-------------------------------------------------------------------
Key: JBMETA-56
URL: http://jira.jboss.com/jira/browse/JBMETA-56
Project: JBoss Metadata
Issue Type: Bug
Security Level: Public(Everyone can see)
Affects Versions: 1.0.0.Beta20, 1.0.0.Beta19
Reporter: Anil Saldhana
Assigned To: Emanuel Muckenhuber
Fix For: 1.0.0.CR1
Consider a ejb-jar.xml snippet:
=========================
<message-driven>
<description>An mdb that access an entity bean as InternalUser to
test propagation of the run-as role through several levels</description>
<ejb-name>DeepRunAsMDB</ejb-name>
<ejb-class>org.jboss.test.security.ejb.RunAsPropagationMDB</ejb-class>
<transaction-type>Container</transaction-type>
<message-driven-destination>
<destination-type>javax.jms.Queue</destination-type>
<subscription-durability>NonDurable</subscription-durability>
</message-driven-destination>
<ejb-local-ref>
<ejb-ref-name>ejb/CalledSessionLocalHome</ejb-ref-name>
<ejb-ref-type>Entity</ejb-ref-type>
<local-home>org.jboss.test.security.interfaces.CalledSessionLocalHome</local-home>
<local>org.jboss.test.security.interfaces.CalledSessionLocal</local>
<ejb-link>Level1MDBCallerBean</ejb-link>
</ejb-local-ref>
<security-identity>
<description>Use a role that is not assigned to any users to
access restricted server side functionallity</description>
<run-as>
<role-name>InternalRole</role-name>
</run-as>
</security-identity>
<resource-ref>
<description>Default QueueFactory</description>
<res-ref-name>jms/QueFactory</res-ref-name>
<res-type>javax.jms.QueueConnectionFactory</res-type>
<res-auth>Container</res-auth>
</resource-ref>
</message-driven>
=========================
Now something for JBossEnterpriseBeanMetaData (Environment env =
bean.getJndiEnvironmentRefsGroup()) should contain the ejb-local refs.
I think the tests need to be updated to handle this case.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6619
days inactive
6620
days old
2 comments
2 participants
participants (2)
-
Anil Saldhana (JIRA) -
Emanuel Muckenhuber (JIRA)