Red Hat Bugzilla – Bug 767981
ESB Deployment ignores directory property
Last modified: 2013-03-14 11:06:39 EDT
Description of problem:
When deploying a new ESB Deployment via JON Gui, no matter what directory you enter in the Deploy directory property, JON puts it in the /deploy directory. Don't know if this is JON or the Profile Service ( a SOA bug was logged by an SA for the same issue https://issues.jboss.org/browse/SOA-3578)
Version-Release number of selected component (if applicable):
The as5 esb plug-in utilizes ProfileService to deploy an ESB Deployment to the AS server. The only option regarding deployment location that appears to be available is deployFarmed and deployExploded.
It would appear that these properties were left over from the as4 version of the ESB plug-in.
Customer wants to deployFarmed via the GUI, the properties in the GUI need to be corrected.
Logged against downstream JBossESB SOA-P bug tracker as https://issues.jboss.org/browse/SOA-3693
The JBoss ESB plug-in is managed/maintained by the JBossESB project.
RH Bugzilla Integration <email@example.com> updated the status of jira SOA-3693 to Closed
SOA team didn't get this fixed in their product in time for their 5.3 release. We will need to wait for the next release to get the fix.
Strike that last comment 7 for the moment. It appears their status shows GA was released but I think that was in error. The release schedule shows a release date of June 1st.
The fix for this has been committed to the upstream ESB project and will be included in the JON 3.1.0.ER5 as per Bug 824185.
verified on JON 3.1.CR3 - there is no longer a directory text field property, but a radio selecting whether deploy farmed or not - which works as expected