Bug 779877 (SOA-2236)

Summary: HornetQ switch for a single configuration
Product: [JBoss] JBoss Enterprise SOA Platform 5 Reporter: Martin Vecera <mvecera>
Component: ToolingAssignee: Julian Coleman <jcoleman>
Status: CLOSED WONTFIX QA Contact:
Severity: high Docs Contact:
Priority: high    
Version: 5.1.0 Dev, 5.1.0.ER1   
Target Milestone: ---   
Target Release: FUTURE   
Hardware: Unspecified   
OS: Unspecified   
URL: http://jira.jboss.org/jira/browse/SOA-2236
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-11-01 20:17:42 UTC Type: Feature Request
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
hornetq-build.xml none

Description Martin Vecera 2010-08-23 11:37:26 UTC 
Complexity: Low
project_key: SOA

Make it possible to use HornetQ configuration switch to be applied to any server configuration specified in a property file.
Comment 1 Len DiMaggio 2010-08-24 13:25:52 UTC 
At present (dev3 build) the tool has the OOTB server configs hardcoded - it would be better if the user could specify the name of the server config that is to have its configuration switched to HornetQ so that user customized configs can be "switched."

In its current form, in order for a user to switch a customer configuration, he/she will have to rename the configuration to one of the OOTB server names before running the tool. This could cause user errors and confusion.
Comment 2 Julian Coleman 2010-09-06 09:51:10 UTC 
The attached replacement for:

  .../extras/hornetq/build.xml

would allow a single profile to be switched to HornetQ by specifying the
properties:

  org.jboss.esb.server.config
  org.jboss.esb.server.clustered

.For example:

  ant -Dorg.jboss.esb.server.config=mine -Dorg.jboss.esb.server.clustered=true

This replacement:

  will not remove JBM from client and common
  will not remove JBM from any profile apart from the specified one
  will install HornetQ in client and common
  will only install HornetQ in the specified profile

Note, that this deviates from the EAP behaviour of changing all profiles.
Comment 3 Julian Coleman 2010-09-06 09:51:10 UTC 
Attachment: Added: hornetq-build.xml
Comment 4 Martin Vecera 2010-09-10 16:04:52 UTC 
Affects ER1 as well but I still did not figure out if this is a possible way. Will know more the next week.