[
http://jira.jboss.com/jira/browse/JBREM-27?page=comments#action_12340029 ]
susanin commented on JBREM-27:
------------------------------
One additional note:
You seem to use the originalURI in the transport() method of HTTPClientInvoker class:
String targetURL = getLocator().getOriginalURI();
But i think that getLocator().getURI() is more correct.
For example, when using annotations we sometimes use the following:
@RemoteBinding(clientBindUrl="http://0.0.0.0:8888/SharedStateManager",jndiBinding="SharedStateManagerhttp")
0.0.0.0 is substituted by the real IP-number of the server during the deployment.
Therefore, the originalURI of the locatoris
http://0.0.0.0:8888/SharedStateManager,
but URI field is correct and set to:
http://x.y.z.w:8888/SharedStateManager
where x.y.z.w is the IP of the server.
With your current code, there is no easy way for a client to get the correct locator,
since
http://0.0.0.0:8888/SharedStateManager is returned. But may be it is also the same
bug somewhere else, which makes use of originalURI, instead of URI.
The fix is obvious and we hope to see it soon in the main branch.
Best regards,
Ivan
Support for HTTP/HTTPS proxy
----------------------------
Key: JBREM-27
URL:
http://jira.jboss.com/jira/browse/JBREM-27
Project: JBoss Remoting
Issue Type: Feature Request
Components: transport
Reporter: Thomas Diesler
Assigned To: Tom Elrod
Priority: Optional
Fix For: 1.2.0 final
This request showed up on the web services forum. Proxies are currently suported in
axis-ws4ee.jar
--
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