Well, I have researched this one now and am stuck again. I'm confused about the following:
1. The "real" WSDL is secured behind SSL. Given the SSL issues before, I'm unable to generate the client stubs using the remote URL. So, I've stored the WSDL to a local file and referenced that to generate the client code. Now, at runtime, I don't know whether I should (or need to) access the "real" WSDL URL, or again reference the local file WSDL. Does it matter? Is it ok if the WSDL is behind SSL? 2. In either case, it seems as if it's pulling the endpoint URL from the WSDL port.address.location attribute. This may or may not be set appropriately by the web service developer, but it doesn't seem like it should matter if I know what the URL is. Can't I override what is specified by the WSDL? As an example, I've exposed my own web services with CXF and the WSDL that is generated has "http://locahost...blah";. Obviously, localhost is not appropriate for anyone else consuming my web services. But an axis2 client is successfully accessing my services since axis2 doesn't seem to rely on the WSDL to get the "real" endpoint URL. I'm sure I'm missing something basic here. Or maybe this is just how the CXF client works and is different than some of the other ws client tools. Thanks for any suggestions. Jim Jim Schneider wrote: > > I now, however, have a different error: > > [java] Payload: > [java] -------------------------------------- > [java] Feb 11, 2010 2:28:24 PM > org.apache.cxf.phase.PhaseInterceptorChain doIntercept > [java] WARNING: Interceptor has thrown exception, unwinding now > [java] org.apache.cxf.binding.soap.SoapFault: Error reading > XMLStreamReader. > [java] at > org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:196) > [java] at > org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:58) > [java] at > org.apache.cxf.phase.PhaseInterceptorChain.doIntercept(PhaseInterceptorChain.java:236) > .... > [java] Caused by: com.ctc.wstx.exc.WstxEOFException: Unexpected EOF > in prolog > [java] at [row,col {unknown-source}]: [1,0] > [java] at > com.ctc.wstx.sr.StreamScanner.throwUnexpectedEOF(StreamScanner.java:686) > [java] at > com.ctc.wstx.sr.BasicStreamReader.handleEOF(BasicStreamReader.java:2134) > [java] at > com.ctc.wstx.sr.BasicStreamReader.nextFromProlog(BasicStreamReader.java:2040) > [java] at > com.ctc.wstx.sr.BasicStreamReader.next(BasicStreamReader.java:1069) > [java] at > com.ctc.wstx.sr.BasicStreamReader.nextTag(BasicStreamReader.java:1095) > [java] at > org.apache.cxf.binding.soap.interceptor.ReadHeadersInterceptor.handleMessage(ReadHeadersInterceptor.java:93) > > but I haven't researched this one yet. > > -- View this message in context: http://old.nabble.com/CXF-client-SSL-pain-tp27551100p27558792.html Sent from the cxf-user mailing list archive at Nabble.com.
