[
http://jira.jboss.com/jira/browse/JBESB-832?page=all ]
Kurt Stam updated JBESB-832:
----------------------------
JBoss Forum Reference:
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=4076306#...
Let's also do this for the jbossesb.xml
${jboss.bind.address} support in ESB configuration files
--------------------------------------------------------
Key: JBESB-832
URL:
http://jira.jboss.com/jira/browse/JBESB-832
Project: JBoss ESB
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: Configuration
Affects Versions: 4.2 Milestone Release 3
Environment: RHEL 5 / JBoss 4.2.1
Reporter: Matt Hicks
Assigned To: Kurt Stam
Fix For: 4.2.1
We use virtual IPs supported by the JBoss binding parameter on startup (e.g. bin/run.sh
-c esb -b 172.17.0.1). However, there are several problems with the ESB configuration
when doing this.
The first file is simple:
* <JBOSS_HOME>/deploy/jbossesb.sar/jbossesb-properties.xml
This file needs every instance of 'localhost' changed to
'${jboss.bind.address}' and it works.
The next 3 files aren't as simple since JBoss doesn't support property
replacement in properties files to my knowledge:
* <JBOSS_HOME>/deploy/juddi-service.sar/juddi.war/WEB-INF/juddi.properties
* <JBOSS_HOME>/deploy/jbossesb.sar/esb.juddi.properties
* <JBOSS_HOME>/deploy/smooks.esb/smooks.esb.properties
These files need to have the same property dynamically looked up based on the binding or
might need to be converted to XML to have the property replaced.
--
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