[jboss-jira] [JBoss JIRA] Assigned: (JBPORTAL-1151) jboss:service=DefaultPartition hardcoded in CMS cluster config

jboss:service=DefaultPartition hardcoded in CMS cluster config -------------------------------------------------------------- Key: JBPORTAL-1151 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1151 Project: JBoss Portal Issue Type: Bug Security Level: Public(Everyone can see) Components: Portal CMS Affects Versions: 2.4.1 Final Reporter: Poul Bildsoee Moeller Assigned To: Sohil Shah Priority: Minor Fix For: 2.4.1 Final When naming my own cluster partition I found that the default name had been hardcoded once in the CMS cluster configuration: In jboss-portal-ha.sar/portal-cms.sar/META-INF/jboss-service.xml The part: <mbean code="org.jboss.portal.jems.ha.HASingletonInvoker" name="portal:service=HASingletonInvoker,type=CMS"> <depends>jboss:service=DefaultPartition</depends> <attribute name="RetryWaitingTimeMS">2000</attribute> <attribute name="MaxRetries">5</attribute> <attribute name="JNDIName">MyServiceInvokeTarget</attribute> <attribute name="JNDIProperties"> java.naming.factory.initial=org.jnp.interfaces.NamingContextFactory java.naming.factory.url.pkgs=org.jboss.naming:org.jnp.interfaces java.naming.provider.url=${jboss.bind.address:localhost}:1100 jnp.disableDiscovery=false jnp.partitionName=${jboss.partition.name:DefaultPartition} jnp.discoveryGroup=${jboss.partition.udpGroup:230.0.0.4} jnp.discoveryPort=1102 jnp.discoveryTTL=16 jnp.discoveryTimeout=5000 jnp.maxRetries=1 </attribute> <depends optional-attribute-name="Callback" proxy-type="attribute">portal:service=CMS</depends> <depends optional-attribute-name="ProxyFactory">portal:service=ProxyFactory,type=CMS</depends> </mbean> where jboss:service=DefaultPartition should be replaced by: jboss:service=${jboss.partition.name:DefaultPartition}