Actually, that doesn't matter. It is a typo, but the software doesn't care what the name of the element is.
It looks like it is true that Axis does not truly support doc/literal =( I was hoping someone would know the answer to this question off the bat.
Thanks
-
Is that a typo in the WSDL??
Is that a typo in the WSDL??? PrderIdentification should be
OrderIdentification i think.
stephen
DealRaider.com wrote:
Thanks for the response.
I tried changing the URN to have '.' in place of the '\' but I get the
same error.
Anybody
Hi ,
Sometime back I had to deal with the same problem. The below mail helped me
out.
Regards,
Dimuthu.
- Original Message -
From: "Tom Jordahl" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>; <[EMAIL PROTECTED]>
Sent: Wednesday, September 03, 2003 9:19 PM
Subject: RE: No such operation fau
Thanks for the response.
I tried changing the URN to have '.' in place of the '\' but I get the
same error.
Anybody have another idea?
DealRaider.com wrote:
Hello,
Thanks to slight hints in previous responses, I think I am now able
to better explain my current issue:
I have a pre-specifi
Have you tried changing the namespace so there are no slashes at all??
Perhaps this will indicate whether it's the namespace that's the problem
or something else.
Also, I don't know the answer to the doc/lit question, have you checked
the samples for doc/lit ??
stephen
DealRaider.com wrote:
Hello,
Thanks to slight hints in previous responses, I think I am now able
to better explain my current issue:
I have a pre-specified WSDL document I'm creating a new Web Service for.
It specifies a doc/literal type style.
I've attached the full WSDL, and also list here some of the key exce