Hide Forgot
Date of First Response: 2010-01-27 04:37:50 Workaround: Workaround Exists Workaround Description: Change line <entry key="juddi.server.name"><xsl:value-of select='$esbHost'/></entry> to <entry key="juddi.server.name">DESIRED_NAME</entry> in bindings-jboss-beans.xml file. project_key: SOA Changing the 'juddi.server.name' property in jbossesb-registry.sar/esb.juddi.xml has no effect. It is overridden by the XSL stylesheet defined in bean EsbJuddiRMIXSLTConfig in bindings-jboss-beans.xml.
Workaround Description: Removed: Change the line <entry key="juddi.server.name"><xsl:value-of select='$esbHost'/></entry> to <entry key="juddi.server.name">DESIRED_NAME</entry> Added: Change line <entry key="juddi.server.name"><xsl:value-of select='$esbHost'/></entry> to <entry key="juddi.server.name">DESIRED_NAME</entry> in bindings-jboss-beans.xml file.
This is correct, it is overridden to support different server bindings.
Thanks Marek. Rejecting as this is a server side configuration parameter that takes its information from service bindings.
I should also add that this parameter is no longer present in juddi 3.0.1, neither is juddi.server.port. They have both been replaced by a single, combined, property called juddi.server.baseurl.