[
http://jira.jboss.com/jira/browse/JBESB-671?page=comments#action_12368416 ]
Kevin Conner commented on JBESB-671:
------------------------------------
The test which failed involved installing two esbs, one of which was scoped.
These esbs have slightly different jboss-esb.xml configurations (they specify different
JMS queues) but they both specify the same action class name.
The scoped version of the esb was supposed to override the action class in the non scoped
version but this was not the case. Messages sent to the scoped esb were therefore
intended to use the scoped version of the action class, resulting in a different response
in the StatsMBean, but only the non scoped action was used.
The scoped action class (in versioned-scoped-src) should have been called MyAction but was
actually called MyJMSListenerAction.
Fix broken scoping tests
------------------------
Key: JBESB-671
URL:
http://jira.jboss.com/jira/browse/JBESB-671
Project: JBoss ESB
Issue Type: Task
Security Level: Public(Everyone can see)
Components: Testing
Reporter: Kevin Conner
Assigned To: Kevin Conner
Fix For: 4.2 Milestone Release 3
There are some standalone tests in the qa/junit directory which test esb scoping. These
tests are currently broken and, from the svn logs, could not possibly have worked since at
least March.
The specific tests (from issue 670) are
> ant one-test -Dtest=server (for the SimpleUnitTestCase)
>
> (and -Dtest=server/jca, and -Dtest=server/ftp for jca and ftp).
--
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