OK, adding elementFormDefault="qualified" to the ?WSDL output file caused
the gSOAP "Warning: part 'msg' uses literal style and must refer to an
element rather than a type." message to go away.
However, going back to what I consider to be the main issue: the XML below.
The only place that it indicates 'test.wsdl.faults2.TestFault' is in the
exceptionName tag. I'm under the impression that exceptionName is an
Axis-specific hack and therefore there is no way that any non-Axis client is
going to be able to deserialize this exception. Sorry to press you on this,
but is my diagnosis correct and is this a bug in Axis?
From: Davanum Srinivas <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: [email protected]
Subject: Re: Exceptions are killing me
Date: Fri, 13 Jan 2006 11:33:34 -0500
2 tips worth trying: (note that Axis has gone thru so many interops
and tck's so i feel this is a gsoap problem)
- try editing the schema and add elementFormDefault="qualified" and
*THEN* generate the code, then use the generated code
- After the prev step, save the dyanmic wsdl
http://localhost:8080/axis/services/FaultService?wsdl, make sure it
still has the qualified (if not add it) then run the gSOAP's
wsdl-to-code generator.
thanks,
dims
On 1/13/06, Jarmo Doc <[EMAIL PROTECTED]> wrote:
> Note that gSOAP 2.7.6c doesn't like test/wsdl/faults2/FaultService.wsdl.
In
> particular it complains that:
>
> Warning: part 'msg' uses literal style and must refer to an element
rather
> than a type
>
>
> >From: "Jarmo Doc" <[EMAIL PROTECTED]>
> >Reply-To: [email protected]
> >To: [EMAIL PROTECTED], [email protected]
> >Subject: Re: Exceptions are killing me
> >Date: Thu, 12 Jan 2006 18:41:39 -0800
> >
> >[Re-sending]
> >
> >OK Dims, here's the XML from the standard Axis 1.3 test/wsdl/faults2
(which
> >is a doc/lit testcase, thus relevant to my situation).
> >
> >I'd say that it's substantially similar to the XML that I personally
see
> >with my custom exceptions, and therefore I would venture to say that
it's
> >*not* fully deserializable by a gSOAP client (because it does not
correctly
> >indicate the embedded exception type).
> >
> ><soapenv:Envelope
xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
> >xmlns:xsd="http://www.w3.org/2001/XMLSchema";
>
>xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";><soapenv:Body><soapenv:Fault>
> > <faultcode>soapenv:Server.generalException</faultcode>
> > <faultstring/>
> > <detail>
> > <msg>
> > <a>throw</a>
> > <b>0</b>
> > <c>throw</c>
> > </msg>
> > <ns1:exceptionName
>
>xmlns:ns1="http://xml.apache.org/axis/";>test.wsdl.faults2.TestFault</ns1:exceptionName>
> > <ns2:hostname
> >xmlns:ns2="http://xml.apache.org/axis/";>myhostname</ns2:hostname>
> > </detail>
> > </soapenv:Fault></soapenv:Body></soapenv:Envelope>
> >
> >This is essentially what I was seeing earlier. What do you think?
Thanks.
> >
> >
> >
> >>From: Davanum Srinivas <[EMAIL PROTECTED]>
> >>Reply-To: [EMAIL PROTECTED]
> >>To: [email protected]
> >>Subject: Re: Exceptions are killing me
> >>Date: Thu, 12 Jan 2006 15:06:57 -0500
> >>
> >>Can u try to see the on the wire serialization is for test\wsdl\faults
> >>example? in a servlet environment? last i check that was fine. it
> >>starts from a wsdl.
> >>
> >>You may need to switch off the hostname and stack trace stuff (see
> >>axis.development.system in
> >>http://ws.apache.org/axis/java/reference.html) for interop with other
> >>stacks.
> >>
> >>thanks,
> >>dims
> >
> >_________________________________________________________________
> >Express yourself instantly with MSN Messenger! Download today - it's
FREE!
> >http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
> >
>
> _________________________________________________________________
> Don't just search. Find. Check out the new MSN Search!
> http://search.msn.click-url.com/go/onm00200636ave/direct/01/
>
>
--
Davanum Srinivas : http://wso2.com/blogs/
_________________________________________________________________
Is your PC infected? Get a FREE online computer virus scan from McAfee®
Security. http://clinic.mcafee.com/clinic/ibuy/campaign.asp?cid=3963
