[jboss-jira] [JBoss JIRA] Updated: (JBPORTAL-1969) WSRP 'self' consumer configuration incorrect if server is configured with non-default ports.

WSRP 'self' consumer configuration incorrect if server is configured with non-default ports. -------------------------------------------------------------------------------------------- Key: JBPORTAL-1969 URL: http://jira.jboss.com/jira/browse/JBPORTAL-1969 Project: JBoss Portal Issue Type: Feature Request Security Level: Public(Everyone can see) Components: Portal WSRP Affects Versions: 2.6.4 Final Environment: JBoss Portal 2.6.3 / JBoss [Trinity] 4.2.2.GA (build: SVNTag=JBoss_4_2_2_GA date=200710221139) Java version: 1.5.0_11,Sun Microsystems Inc. Java VM: Java HotSpot(TM) Client VM 1.5.0_11-b03,Sun Microsystems Inc. OS-System: Windows 2000 5.0,x86 Reporter: Andreas Chlupacek Assigned To: Chris Laprun Priority: Optional Fix For: 2.8 Final The portal server's service bindings were altered in JBOSS_HOME/server/default/conf/jboss-service.xml so that the server loads its bindings from the "ports-01" configuration specified in JBOSS_HOME/docs/examples/binding-manager/sample-bindings.xml. Steps to reproduce: =================== In the Admin Portal, navigate to the WSRP Page and inspect the consumers configuration. The "self" consumer is shown as "(inactive) (refresh needed)". Click on "Configure" and inspect the endpoint configuration (make sure the "Use WSDL?" checkbox is not ticked). Observed behaviour: =================== The endpoint URLs point to port 8080 regardless of the listening ports stated in the service binding configuration. This causes the "self" consumer to be inactive after server startup, with the corresponding error messages shown on the console ("InvokerUnavailableException: Couldn't register with producer 'self'"). Expected behaviour: =================== The endpoint configuration should reflect the server's listening ports.