[
http://jira.jboss.com/jira/browse/JBAS-3444?page=comments#action_12340443 ]
Jaroslaw Kijanowski commented on JBAS-3444:
-------------------------------------------
I don't know what exactly has changed now, but i checked out the AS and run the ENC
test and now i've got an NameNotFoundException, because DefaultDS is not bound. But my
last resolve was wrong, too, because adding the queues and topics during the startup of
the server causes other tests to fail, which try to deploy their own queues. I've got
a new solution. ENCUnitTestCase should provide its own queues/topics during the test. This
is done by changing jboss-head/testsuite/imports/sections/naming.xml:
from:
<fileset dir="${build.resources}/naming/services">
<include name="jaas-config.xml"/>
<include name="login-config-service.xml"/>
</fileset>
</jar>
to:
<fileset dir="${build.resources}/naming/services">
<include name="jaas-config.xml"/>
<include name="login-config-service.xml"/>
</fileset>
<fileset dir="${source.resources}/messaging">
<include name="test-destinations-full-service.xml"/>
</fileset>
</jar>
******************************
naming.jar is deployed during the ENC test and this works fine. The necessary
queues/topics are bound at the beginning of the test and then unbound at the end of the
test, so other tests don't fail trying to deploy their queues. if this soution is ok,
i'll try to develop a patch.
Maybe "test-destinations-full-service.xml" should be in the
{build.resources}/naming, so deleting this file from ${source.resources}/messaging would
not cause an unexpected error in some weeks/months/years?
Sory for the continous changing of my solutions, but this is the last one :)
org.jboss.test.naming.test.ENCUnitTestCase ends with errors
-----------------------------------------------------------
Key: JBAS-3444
URL:
http://jira.jboss.com/jira/browse/JBAS-3444
Project: JBoss Application Server
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Test Suite
Affects Versions: JBossAS-5.0.0.Beta
Environment: win xp
Reporter: Jaroslaw Kijanowski
Assigned To: Anil Saldhana
org.jboss.test.naming.test.ENCUnitTestCase ends with two errors, because nessesary queues
and topics aren't present for the "all" instance.
ENCUnitTestCase calls accessENC() method in org.jboss.test.naming.ejb.TestEncBean.java.
The last two methods of the if-block (testResourceEnvEntries and
testMessageDestinationRefs) cause NameNotFoundException: testQueue not bound.
They try to use the queues "res/aQueue" and
"mdr/ConsumesProducesJNDIName". These queues are "mapped" in the
jboss-head/testsuite/src/resources/naming/jar/META-INF/jboss.xml to
"queue/testQueue" and "queue/A", but these two queues don't
exist.
The last method (testMessageDestinationRefs) try to use also the topic
"mdr/ProducesLink", which is "mapped" in
jboss-head/testsuite/src/resources/naming/jar/META-INF/ejb-jar.xml to
"TestTopic" which is "mapped" in
jboss-head/testsuite/src/resources/naming/jar/META-INF/jboss.xml to
"topic/testTopic" cause an errror, because the tpic isnt't present too.
To fix these errors:
uncomment the two queues "testQueue" and "A" and the first topic
"testTopic" in:
jboss-head\build\output\jboss-5.0.0.Beta\server\all\deploy-hasingleton\jms\jbossmq-destinations-service.xml
--
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