Anton, The only problem I see with the WSDL is the inclusion of the encodingStyle attribute in the <soap:body> declarations in the binding. Remove these and try regenerating the service and the client stub.
The error, "Unexpected subelement" is caused by the fact that the ssoLoginRet element is qualified in the return message. When using RPC style, the generated accessor elements for the message part must be unqualified. If Axis2 manages to get past that point, it would generate the same error when it encounters the children of ssoLoginRet because those elements are unqualified, but they should be qualified. (Your schema specifies elementFormDefault="qualified"). Anne On 4/12/07, Anton Pirker <[EMAIL PROTECTED]> wrote:
Hi! I got the WSDL from a client of mine. Here you have the complete WSDL. (see attachment) But xmlspy says the wsdl is valid and well-formed, so i thought everything is ok... anton Anne Thomas Manes wrote: > Anton, > > I just looked at the binding again, and realized that it says > use="literal" and also specifies encodingStyle. This is not a valid > WSDL. You cannot specify an encoding style when use="literal". > > Where did you get this WSDL? > > It would be helpful if you provided us with the complete WSDL. > > Anne > > On 4/12/07, Anne Thomas Manes <[EMAIL PROTECTED]> wrote: >> The service requires that you send a message encoded using >> rpc/encoding. Because Axis2 does not support SOAP encoding, you can't >> use it to build a client for this service. Try Axis 1.4 instead. >> >> Anne >> >> On 4/11/07, Anton Pirker <[EMAIL PROTECTED]> wrote: >> > Hi Anne! >> > >> > Anne Thomas Manes wrote: >> > > Axis2 does not support rpc/encoding. >> > >> > Does this mean that i can completely forget to implement a client for >> > the service? >> > >> > Or can i just change the binding from rpc to document and everything >> > will be fine? >> > (i will try this tomorrow morning in the office, from my home-office i >> > do not have access to the service) >> > >> > >> > >> > Anton >> > >> > >> > >> > >> > --------------------------------------------------------------------- >> > To unsubscribe, e-mail: [EMAIL PROTECTED] >> > For additional commands, e-mail: [EMAIL PROTECTED] >> > >> > >> > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
