]
Chris Laprun resolved GTNWSRP-134.
----------------------------------
Fix Version/s: (was: 2.2.0)
Resolution: Won't Fix
WSRP 'self' consumer configuration incorrect if server is
configured with non-default ports.
--------------------------------------------------------------------------------------------
Key: GTNWSRP-134
URL:
https://issues.jboss.org/browse/GTNWSRP-134
Project: GateIn WSRP
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Affects Versions: 1.1.1-GA
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
Assignee: Chris Laprun
Priority: Optional
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.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: