That seems to be an OLD MS based service.  Most likely, turning chunking 
off will fix it.  

import org.apache.cxf.endpoint.Client;
import org.apache.cxf.frontend.ClientProxy;
import org.apache.cxf.transport.http.HTTPConduit;

        HPRequestWSSoap port = ss.getHPRequestWSSoap();  
        Client client = ClientProxy.getClient(port);
        HTTPConduit httpConduit = (HTTPConduit) client.getConduit();
        httpConduit.getClient().setAllowChunking(false);

You might also need:

import org.apache.cxf.configuration.jsse.TLSClientParameters;

        TLSClientParameters tlsParams = new TLSClientParameters();
        tlsParams.setSecureSocketProtocol("SSL");
        httpConduit.setTlsClientParameters(tlsParams);


Dan




On Friday 29 February 2008, yulinxp wrote:
> I was trying to use cxf client. But it didn't work for me. Here is my
> post:
> http://www.nabble.com/client-SSL-question-td15564062.html#a15564062
>
> To summarize my problem:
> I need to access the web service here:
> https://mdf.ingenixmedpoint.com/mdfwebservices/hprequest.asmx?WSDL
> I can't connect to url directly because of the unknown host.
> I save that wsdl file and change <soap:address>
> <soap:address
> location="https://mdf.ingenixmedpoint.com/mdfwebservices/hprequest.asm
>x?WSDL"/>
>
> Now using NET, I can connect to it!  Using wsimport, I can connect
> too! But CXF client doesn't work! The message could be sent!
>
> Caused by: java.io.IOException: Not Found
>         at
> org.apache.cxf.transport.http.HTTPConduit$WrappedOutputStream.handleRe
>sponse(HTTPConduit.java:1888)
>
> The exception doesn't make sense. So I guess this is a bug in cxf
> client.
>
> dkulp wrote:
> > That all said, can I ask the reason for NOT using CXF for the
> > client?
> >
> > Dan
> >
> > On Friday 29 February 2008, Daniel Kulp wrote:
> >> Honestly, I'm not sure there IS a way.   I was hoping for at least
> >> a system property, but looking at the code for jaxws-api, the
> >> system property is actually checked last.  :-(
> >>
> >> The only way I can come up with that MIGHT work is to create a
> >> special classloader that blocks the call to
> >> getResource("META-INF/services/javax.xml.ws.spi.Provider") and just
> >> returns null.   Set the thread.contextClassLoader to that
> >> classloader just before the call to "new HPRequestWS()".  Probably
> >> should reset it back to the original when done.
> >>
> >> Dan
> >>
> >> On Friday 29 February 2008, yulinxp wrote:
> >> > Those classes generated by wsimport and CXF client are very
> >> > similar. For HPRequestWS ss = new HPRequestWS();
> >> >
> >> > wsimport version:
> >> > ss-->delegate: [EMAIL PROTECTED]
> >> >
> >> > CXF version:
> >> > ss-->delegate: [EMAIL PROTECTED]
> >> >
> >> > How can I force it use WSServiceDelegate not cxf ServiceImpl???
> >> > Please help!
> >
> > --
> > J. Daniel Kulp
> > Principal Engineer, IONA
> > [EMAIL PROTECTED]
> > http://www.dankulp.com/blog



-- 
J. Daniel Kulp
Principal Engineer, IONA
[EMAIL PROTECTED]
http://www.dankulp.com/blog

Reply via email to