Title: RE: problem using WSDL2Java on RPC/Literal
Why is it necessary to put the element
into a specific namespace? Is this a pre-existing service that you can’t
modify? If so, then I think your best bet is to define the service as
Document/Literal, and then you can specify the exact
Title: RE: problem using WSDL2Java on RPC/Literal
Why is it necessary to put the element
into a specific namespace? Is this a pre-existing service that you can’t
modify? If so, then I think your best bet is to define the service as
Document/Literal, and then you can specify the exact
Title: RE: problem using WSDL2Java on RPC/Literal
Hmmm, maybe it's time I take a look at that WS-I Basic Profile. Thanks for the help guys. I guess I'll just have to figure out a workaround then.
-Wei
-Original Message-
From: Anne Thomas Manes [mailto:[EMAIL PROTECT
u must use
Document/Literal rather than RPC/Literal.
[1] http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html
Regards,
Anne
-Original Message-
From: Robert Lowe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 13, 2004 3:28 PM
To: [EMAIL PROTECTED]
Subject: RE: problem using WS
u must use
Document/Literal rather than RPC/Literal.
[1] http://www.ws-i.org/Profiles/Basic/2003-08/BasicProfile-1.0a.html
Regards,
Anne
-Original Message-
From: Robert Lowe [mailto:[EMAIL PROTECTED]
Sent: Tuesday, April 13, 2004 3:28 PM
To: [EMAIL PROTECTED]
Subject: RE: problem using WS
Title: RE: problem using WSDL2Java on RPC/Literal
Thanks for the tip.
I am creating RPC/Literal WSDL's because the services I'm writing for is somewhat of a legacy system that employs a hybrid approach between RPC/Encoded and RPC/Literal. While I would love to move to doc/
I'm not sure what support Axis has for RPC/Literal (if any), but it seems
to be doing the right thing in this case. By definition, in an RPC/Literal
message, the part names (in your case, SalesOrder) are simply wrappers and
are NOT to be namespace-qualified. Hence you see the xmlns="" which sa
If your schema specifies elementFormDefault="unqualified", or does not
specify the elementFormDefault attribute at all, then Axis is doing the
correct thing.
Try adding elementFormDefault="qualified" to your schema.
Best regards,
Robert Lowe
http://RMLowe.com/
-Original Message-
From
