[JBoss JIRA] Created: (EJBTHREE-1633) setMessageDrivenContext callback is not made to optional MessageDriven interface
2:30 a.m.
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
Environment: EJB3 Integration TestSuite:
org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testQueue
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Fix For: 1.0.0-CR1
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
2:32 a.m.
New subject: [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....
]
Andrew Lee Rubinger commented on EJBTHREE-1633:
-----------------------------------------------
Applying the workaround is not quite enough to pass "dd/mdb" tests:
Testsuite: org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase
Tests run: 10, Failures: 3, Errors: 0, Time elapsed: 100.467 sec
Testcase: testQueue took 13.313 sec
Testcase: testTopic took 10.173 sec
Testcase: testObjectMessage took 0.191 sec
Testcase: testNoQueueConstructionForAlreadyExists took 0.022 sec
Testcase: testNoTopicConstructionForAlreadyExists took 0.009 sec
Testcase: testDurableTopic took 10.526 sec
FAILED
MDB failed to receive messages on topic/testDurableTopic expected:<10> but
was:<20>
junit.framework.AssertionFailedError: MDB failed to receive messages on
topic/testDurableTopic expected:<10> but was:<20>
at org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testTopic(MDBUnitTestCase.java:208)
at
org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testDurableTopic(MDBUnitTestCase.java:280)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
Testcase: testQueueEx took 10.209 sec
FAILED
expected:<100> but was:<99>
junit.framework.AssertionFailedError: expected:<100> but was:<99>
at org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testQueue(MDBUnitTestCase.java:173)
at org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testQueueEx(MDBUnitTestCase.java:285)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
Testcase: testQueueA took 10.258 sec
FAILED
expected:<10> but was:<9>
junit.framework.AssertionFailedError: expected:<10> but was:<9>
at org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testQueue(MDBUnitTestCase.java:173)
at org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testQueueA(MDBUnitTestCase.java:290)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
at junit.extensions.TestDecorator.basicRun(TestDecorator.java:24)
at junit.extensions.TestSetup$1.protect(TestSetup.java:23)
at junit.extensions.TestSetup.run(TestSetup.java:27)
Testcase: testWaitForCompletion took 20.001 sec
Testcase: testQueueB took 10.2 sec
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
Environment: EJB3 Integration TestSuite:
org.jboss.ejb3.test.dd.mdb.unit.MDBUnitTestCase.testQueue
Reporter: Andrew Lee Rubinger
Assignee: Andrew Lee Rubinger
Fix For: 1.0.0-CR1
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
1:20 p.m.
New subject: [JBoss JIRA] Updated: (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 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
4:27 p.m.
New subject: [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
4:33 p.m.
New subject: [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....
]
Andrew Lee Rubinger commented on EJBTHREE-1633:
-----------------------------------------------
Optional in the sense that we don't have to call it if MessageDrivenBean is not
implemented. If it is, I believe we do have to invoke it.
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
5153
days inactive
5618
days old
4 comments
2 participants
participants (2)
-
Andrew Lee Rubinger (JIRA) -
Carlo de Wolf (JIRA)