[jboss-jira] [JBoss JIRA] Updated: (EJBTHREE-1633) setMessageDrivenContext callback is not made to optional MessageDriven interface
Carlo de Wolf (JIRA)
jira-events at lists.jboss.org
Wed Jan 7 07:20:04 EST 2009
[ https://jira.jboss.org/jira/browse/EJBTHREE-1633?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Carlo de Wolf updated EJBTHREE-1633:
------------------------------------
Fix Version/s: (was: 1.0.0-CR1)
Affects Version/s: 1.0.0
Labels: known_issue (was: )
> setMessageDrivenContext callback is not made to optional MessageDriven interface
> --------------------------------------------------------------------------------
>
> Key: EJBTHREE-1633
> URL: https://jira.jboss.org/jira/browse/EJBTHREE-1633
> Project: EJB 3.0
> Issue Type: Bug
> Components: core
> Affects Versions: 1.0.0
> Environment: EJB3 Integration TestSuite: org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testQueue
> Reporter: Andrew Lee Rubinger
> Assignee: Andrew Lee Rubinger
>
> The required callback to setMessageDrivenContext is not made in MDBs
> EJB 3.0 Core 5.4.6:
> The setMessageDrivenContext method is called by the bean's container to associate a mes-
> sage-driven bean instance with its context maintained by the container.
--
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 jboss-jira
mailing list