[
http://jira.jboss.com/jira/browse/JBESB-1056?page=comments#action_12377292 ]
Kevin Conner commented on JBESB-1056:
-------------------------------------
Sorry but there is *no* install stage of JBoss Messaging, the base zip used to create the
jbossesb-server already contains it.
As to esb-config.xml, the paths used in this drive our product/QA tests. If they were
wrong then they would not pass.
Also, the paths can be configured in multiple places because the scripts are used in the
distribution as well as during build. The esb-config.xml does not exist in the
distribution and is used in the build to *overrides* the other definitions.
Management console in ESB server uses JBossMQ instead of JBoss
Messaging
------------------------------------------------------------------------
Key: JBESB-1056
URL:
http://jira.jboss.com/jira/browse/JBESB-1056
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Tooling
Affects Versions: 4.2.1 IR1
Environment: Sun JVM, ant 1.6.5
Reporter: Martin Vecera
Assigned To: Mark Little
I've checked out the ESB from trunk and run 'ant dist'.
The file product/build/jbossesb-server-4.2.1IR1/server/default/deploy/management.esb
contains jbmq-queue-service.xml instead of jbm-queue-service.xml. This is because
product/tools/console/management-esb/build.xml is checking for JBoss Messaging in deploy
directory before Messaging is installed there and therefore it switches to JBossMQ. Using
JBossMQ in management.esb causes an exception being thrown during server startup.
--
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