You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@cxf.apache.org by Jo...@barclayscapital.com on 2009/02/12 12:37:25 UTC
Client debuggign
Hello,
After generating a set of stub from a WSDL, is it possible to switch on
some HTTP level debug in order to trace why a WS call failed? When I
attempt to invoke a service I see the following, however changing the
location in the WSDL to localhost:1234, and running netcat, reveals it
is opening the socket and making the call. So I guess I need to see the
server response.
Exception in thread "main" java.lang.IllegalArgumentException: faultCode
argument for createFault was passed NULL
at
com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl.creat
eFault(SOAPFactory1_1Impl.java:56)
at
com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fau
lt.java:164)
at
com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFault
Builder.java:94)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHa
ndler.java:240)
at
com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHa
ndler.java:210)
at
com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
at $Proxy33.createChange(Unknown Source)
Thanks.
_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group.
_______________________________________________
RE: Client debuggign
Posted by Jo...@barclayscapital.com.
Oops :-) I stupidly thought that maven's eclipse:eclipse target would
set up my project correctly. I stand corrected.
Thanks Dan - I thought CXF made use of the Sun libraries in some way.
> -----Original Message-----
> From: Daniel Kulp [mailto:dkulp@apache.org]
> Sent: 12 February 2009 16:04
> To: users@cxf.apache.org
> Cc: Baker, John: IT (LDN)
> Subject: Re: Client debuggign
>
>
> Well, from your stack trace, you aren't using CXF. You are
> using the jaxws
> client built into Java 6. Thus, anything I tell you won't
> help at all. :-)
> First step would be to make sure the cxf jars are on the
> classpath and being
> picked up properly. :-)
>
> Dan
>
>
>
>
>
> On Thu February 12 2009 6:37:25 am
> John.Baker@barclayscapital.com wrote:
> > Hello,
> >
> > After generating a set of stub from a WSDL, is it possible
> to switch
> > on some HTTP level debug in order to trace why a WS call
> failed? When
> > I attempt to invoke a service I see the following, however changing
> > the location in the WSDL to localhost:1234, and running netcat,
> > reveals it is opening the socket and making the call. So I guess I
> > need to see the server response.
> >
> > Exception in thread "main" java.lang.IllegalArgumentException:
> > faultCode argument for createFault was passed NULL
> > at
> >
> com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl.cre
> > at
> > eFault(SOAPFactory1_1Impl.java:56)
> > at
> >
> com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11F
> > au
> > lt.java:164)
> > at
> >
> com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFau
> > lt
> > Builder.java:94)
> > at
> >
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethod
> > Ha
> > ndler.java:240)
> > at
> >
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethod
> > Ha
> > ndler.java:210)
> > at
> > com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
> > at $Proxy33.createChange(Unknown Source)
> >
> > Thanks.
> > _______________________________________________
> >
> > This e-mail may contain information that is confidential,
> privileged
> > or otherwise protected from disclosure. If you are not an intended
> > recipient of this e-mail, do not duplicate or redistribute
> it by any
> > means. Please delete it and any attachments and notify the
> sender that
> > you have received it in error. Unless specifically indicated, this
> > e-mail is not an offer to buy or sell or a solicitation to
> buy or sell
> > any securities, investment products or other financial product or
> > service, an official confirmation of any transaction, or an
> official
> > statement of Barclays. Any views or opinions presented are solely
> > those of the author and do not necessarily represent those of
> > Barclays. This e-mail is subject to terms available at the
> following
> > link: www.barcap.com/emaildisclaimer. By messaging with
> Barclays you
> > consent to the foregoing. Barclays Capital is the
> investment banking
> > division of Barclays Bank PLC, a company registered in
> England (number
> > 1026167) with its registered office at 1 Churchill Place, London,
> > E14 5HP. This email may relate to or be sent from other members of
> > the Barclays Group. _______________________________________________
>
> --
> Daniel Kulp
> dkulp@apache.org
> http://www.dankulp.com/blog
>
_______________________________________________
This e-mail may contain information that is confidential, privileged or otherwise protected from disclosure. If you are not an intended recipient of this e-mail, do not duplicate or redistribute it by any means. Please delete it and any attachments and notify the sender that you have received it in error. Unless specifically indicated, this e-mail is not an offer to buy or sell or a solicitation to buy or sell any securities, investment products or other financial product or service, an official confirmation of any transaction, or an official statement of Barclays. Any views or opinions presented are solely those of the author and do not necessarily represent those of Barclays. This e-mail is subject to terms available at the following link: www.barcap.com/emaildisclaimer. By messaging with Barclays you consent to the foregoing. Barclays Capital is the investment banking division of Barclays Bank PLC, a company registered in England (number 1026167) with its registered office at 1 Churchill Place, London, E14 5HP. This email may relate to or be sent from other members of the Barclays Group.
_______________________________________________
Re: Client debuggign
Posted by Daniel Kulp <dk...@apache.org>.
Well, from your stack trace, you aren't using CXF. You are using the jaxws
client built into Java 6. Thus, anything I tell you won't help at all. :-)
First step would be to make sure the cxf jars are on the classpath and being
picked up properly. :-)
Dan
On Thu February 12 2009 6:37:25 am John.Baker@barclayscapital.com wrote:
> Hello,
>
> After generating a set of stub from a WSDL, is it possible to switch on
> some HTTP level debug in order to trace why a WS call failed? When I
> attempt to invoke a service I see the following, however changing the
> location in the WSDL to localhost:1234, and running netcat, reveals it
> is opening the socket and making the call. So I guess I need to see the
> server response.
>
> Exception in thread "main" java.lang.IllegalArgumentException: faultCode
> argument for createFault was passed NULL
> at
> com.sun.xml.internal.messaging.saaj.soap.ver1_1.SOAPFactory1_1Impl.creat
> eFault(SOAPFactory1_1Impl.java:56)
> at
> com.sun.xml.internal.ws.fault.SOAP11Fault.getProtocolException(SOAP11Fau
> lt.java:164)
> at
> com.sun.xml.internal.ws.fault.SOAPFaultBuilder.createException(SOAPFault
> Builder.java:94)
> at
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHa
> ndler.java:240)
> at
> com.sun.xml.internal.ws.client.sei.SyncMethodHandler.invoke(SyncMethodHa
> ndler.java:210)
> at
> com.sun.xml.internal.ws.client.sei.SEIStub.invoke(SEIStub.java:103)
> at $Proxy33.createChange(Unknown Source)
>
> Thanks.
> _______________________________________________
>
> This e-mail may contain information that is confidential, privileged or
> otherwise protected from disclosure. If you are not an intended recipient
> of this e-mail, do not duplicate or redistribute it by any means. Please
> delete it and any attachments and notify the sender that you have received
> it in error. Unless specifically indicated, this e-mail is not an offer to
> buy or sell or a solicitation to buy or sell any securities, investment
> products or other financial product or service, an official confirmation of
> any transaction, or an official statement of Barclays. Any views or
> opinions presented are solely those of the author and do not necessarily
> represent those of Barclays. This e-mail is subject to terms available at
> the following link: www.barcap.com/emaildisclaimer. By messaging with
> Barclays you consent to the foregoing. Barclays Capital is the investment
> banking division of Barclays Bank PLC, a company registered in England
> (number 1026167) with its registered office at 1 Churchill Place, London,
> E14 5HP. This email may relate to or be sent from other members of the
> Barclays Group. _______________________________________________
--
Daniel Kulp
dkulp@apache.org
http://www.dankulp.com/blog