On Tue, 2004-03-02 at 01:46, Dan Christopherson wrote: > If you had WSDL that you hand-built in XML-Spy (which is the right way > to go, IMHO), why were you trying to use the generated WSDL? I wouldn't > do that if I were you - I wouldn't really expect it to work. I'm not > confident that the WSDL->Java->WSDL conversion process will give back > the original WSDL in all cases.
The reasons are two folded. The first reason is that, at least I thought so, if Axis could generate the WSDL I guessed it could handle the generated code. That seemed not to be the case with Doc/Literal. The other problem I have is that if the WSDL contains a <choice> this will be implemented in Axis as an <sequence> and later in the Java->WSDL it is still a <sequence>. How can I (I have not tested this yet) be sure that the Axis Service will understand the <choice> from the Original WSDL? I might be wrong here and that it actual is better to use the original WSDL. > Axis' support for Doc/Literal is getting better all the time - what > version were/are you working with? Axis 1.1 /Magnus > -danch > > > Magnus Sandberg wrote: > > I have seen quite a bit of post here on interoperability and problems > > with Axis not generation WSDL as expected. > > > > I have been trying for some time to deploy a quite large service, using > > Axis 1.1, with about a hundred functions and very deep complex data > > structures, including Arrays. > > > > Just want to share a few things that I have found out on my journey to > > success and to ask a few thing that don't work as I want them to. > > > > We are building our service from WSDL that we create in XML-spy, in out > > first attempt we tried to generate a Doc/Literal Service. WSDL2Java > > successfully generated java classes for us but when we tried to generate > > WSDL from the running service (using ?WSDL) Axis kept on giving us > > errors like this: > > > > ---8<---- > > Fault - WSDLException: faultCode=PARSER_ERROR: Problem parsing '- WSDL > > Document -'.: The value of the attribute > > "prefix="xmlns",localpart="tns1",rawname="xmlns:tns1"" is invalid. > > Prefixed namespace bindings may not be empty.: > > org.xml.sax.SAXParseException: The value of the attribute > > "prefix="xmlns",localpart="tns1",rawname="xmlns:tns1"" is invalid. > > Prefixed namespace bindings may not be empty. > > ---8<----- > > > > After searching, reading and experimenting quite a bit we found out that > > Axis doesn't really like Doc/Literal so we tried RPC/Encoded instead. > > (Note that .NET only likes Doc/Literal or RPC/Encoded and no other > > combinations.) Now Axis could generate the WSDL and we started to build > > clients. Using Axis as client was no problem but the .NET client gave us > > this error: > >
