Open glassfishrobot opened 16 years ago
Reported by carstensis@java.net
jitu@java.net said: Assigning it to myself.
nickwi@java.net said: I've created a patch for this that allows a custom PortAddressResolver to be declared on the web service endpoint class using an annotation:
.... @CustomPortAddressResolver( resolver = MyPortAddressResolver.class ) @WebService......
I've attached the annotation class and a modified HttpAdapter class. This has been modified from JAX-WS 2.1.3.
nickwi@java.net said: Created an attachment (id=255) CustomPortAddressResolver
nickwi@java.net said: Created an attachment (id=256) HttpAdapter
psartini said:
We ran into this problem as well. Our use case is a proxy server that rewrites the path.
api.domain.com/soap/v3 -> localhost:8080/
The domain ist easy to change with the http-listener - but we need to define the path as well.
flaviobp said: Anyone can give some hints where to search or give a solution?
File: CustomPortAddressResolver.java Attached By: nickwi@java.net
File: HttpAdapter.java Attached By: nickwi@java.net
Was assigned to jitu@java.net
This issue was imported from java.net JIRA JAX_WS-602
There are cases where it is not desirable for the soap:address location of a published WSDL to be derived from the WSDL request URL or even from the servlet container. That might be firewall/proxy scenarios, where the baseAddress of the forwarded WSDL request or the servlet container is not reachable from the outside and therefore should not be put in the soap:address of the published WSDL.
A possible solution would be to introduce a new option for the sun-jaxws.xml that contains the full URL of the Endpoint to be put as soap:address in the published WSDL (like the "publishedEndpointUrl" option does in CXF, see https://issues.apache.org/jira/browse/CXF-1279).
See also the forum thread: http://forums.java.net/jive/thread.jspa?messageID=290807
Environment
Operating System: All Platform: All
Affected Versions
[2.0 FCS]