This week's book giveaway is in the OO, Patterns, UML and Refactoring forum. We're giving away four copies of Refactoring for Software Design Smells: Managing Technical Debt and have Girish Suryanarayana, Ganesh Samarthyam & Tushar Sharma on-line! See this thread for details.
For some reason, the same logic that works locally, fails when trying to connect remotely.
The WSDL is alive and up. I created the client WS code using that WSDL.
Yet, when I call it the same way I do the local code, it fails with the error stack below.
The main method code that sets up the endpoint looks like this:
I've tried the hard coded path to the remote server's actual "WWW" address, with the same results.
Exception in thread "main" javax.xml.ws.soap.SOAPFaultException: java.lang.NullPointerException at com.sun.xml.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fault.java:163)
at $Proxy29.getCitiesFromZip(Unknown Source)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
Any suggestions would be greatly appreciated.
Joined: Jul 12, 2002
This is fixed.
Just a case issue in persistence.xml....the database had to match case with what was in MySQL.
I’ve looked at a lot of different solutions, and in my humble opinion Aspose is the way to go. Here’s the link: http://aspose.com
subject: Web Service Client Works Locally, but not with Remote Server