Issue Details (XML | Word | Printable)

Key: GLASSFISH-2889
Type: Bug Bug
Status: Open Open
Priority: Minor Minor
Assignee: Bhakti Mehta
Reporter: kretes
Votes: 0
Watchers: 1
Operations

If you were logged in you would be able to see more operations.
glassfish

bad address of WSDL Schema and soap binding while glassfish in NAT network

Created: 22/Apr/07 09:19 PM   Updated: 06/Mar/12 09:57 PM
Component/s: web_services
Affects Version/s: 9.0peur1
Fix Version/s: not determined

Time Tracking:
Not Specified

Environment:

Operating System: All
Platform: All


Issuezilla Id: 2,889
Tags:
Participants: Bhakti Mehta, gfbugbridge, kretes and Tom Mueller


 Description  « Hide

When machine's ip is some kind of 192.168.0.2 and machine is visible from the
internet under some other public IP due to routing doesn't matter if You connect
to some WSDL using public ip, or local network ip, in wsdl there is always
rerference to '192.168.0.2', which is not accessible from all over the internet.
for example
<xsd:import namespace="http://webservices/"
schemaLocation="http://192.168.0.10:8080/UserWebServiceService/UserWebService/__container$publishing$subctx/META-INF/wsdl/UserWebServiceService_schema1.xsd"/>
</xsd:schema>

and same in soap binding in the end of wsdl
Similiar discussions:
https://glassfish.dev.java.net/servlets/ReadMsg?list=users&msgNo=2739
and
https://glassfish.dev.java.net/servlets/ReadMsg?list=users&msgNo=1801

Workaround : download wsdl file and change manually all entries before using it
in some tool.



No work has yet been logged on this issue.