[jboss-jira] [JBoss JIRA] Commented: (EJBTHREE-1633) setMessageDrivenContext callback is not made to optional MessageDriven interface
[
https://jira.jboss.org/jira/browse/EJBTHREE-1633?page=com.atlassian.jira....
]
Carlo de Wolf commented on EJBTHREE-1633:
-----------------------------------------
EJB 3.1 FR / 3.0 5.4.6 The Optional MessageDrivenBean Interface:
"The message-driven bean class is not required to implement the
javax.ejb.MessageDrivenBean interface.
The MessageDrivenBean interface defines two methods, setMessageDrivenContext and
ejbRemove.
The setMessageDrivenContext method is called by the bean's container to associate a
message-driven bean instance with its context maintained by the container. Typically a
message-driven bean instance retains its message-driven context as part of its
state."
If a bean does not implement MessageDrivenBean, there is no 'the
setMessageDrivenContext' method.
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-GA
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