I don't know about non-Java web services clients, but I can confirm Russell's experience with Axis 1.4. I fixed it with exactly the same change. It also happens on any response output values, which was not quite as elegant to patch in the generated stubs.
I don't know if it's an Axis bug or a Remedy issue, but I can say that Remedy and Axis' wsdl2java are certainly incompatible. Dan -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Wade Wiles Sent: Thursday, August 24, 2006 3:11 PM To: [email protected] Subject: Re: AR WebServices not parsing ok Thanks, But, does anybody know if this is an AXIS bug or remedy issue? I've got to use Java, and frankly, we have this build process fairly automated and manually editing the stubs isn't so elegant. Also, are there other non-java clients that are experiencing this? I'm also wondering if this is a wsi compliance issue. Thanks, Wade Wiles EAI & Web Services Development XO Communications [EMAIL PROTECTED] _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
