Classification: UNCLASSIFIED I had the same error but fixed it like Dan Hardy said, but now the issue is when it tries to come back it says that it cannot find the return value. This is because for some reason creating a default Web Service on Remedy's side does not set the default namespace (xmlns) and instead it just leaves it out, this seems to cause the client not to know what it should be reading. It seems to be that way anyways since in 7.0 it doesn't work, but in 5.1/6.3 it does work, the only difference in the WSDL's is the fact that xmlns is not in the WSDL for 7.0.
-----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Carey Matthew Black Sent: July 19, 2006 2:44 PM To: [email protected] Subject: Re: Problem consuming Remedy web services using Axis Stephen, Be aware that the WSDL may require an element when the form does not require a value. You have to set the elements to be "nillable" (I think) in the Remedy Web service for it to allow the client to "not bother to send those elements at all." Apparently "Required/Optional" values are not _by default_ translated into the "nillable" operation/parts of the WSDL that is generated. ( In theory the WS client should deal with those parts too, but....) -- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. Never ascribe to malice, that which can be explained by incompetence. On 7/19/06, Stephen Earl <[EMAIL PROTECTED]> wrote: > Our WSDL is a remedy auto-generated one and the fields are in the WSDL > however very few of them are officially 'required' but are optional. > > The people wanting to use my webservice have been given a list of the > required fields and that's what they are sending, so they aren't > sending all the fields in the WSDL but are sending all the fields that > are 'mapped' inside the webservice. > > I wasn't aware the mid-tier log would show us the whole transaction so > we'll give that a shot in the morning. > > Stephen > > On 19/07/06, Grooms, Frederick W <[EMAIL PROTECTED]> wrote: > > ** > > With the mid-Tier logs set to the most detailed it will show you the > > XML being sent to Remedy. What does it look like compared to the > > XML structure in the WSDL? > > > > Fred > > ________________________________ > > From: Action Request System discussion list(ARSList) > > [mailto:[EMAIL PROTECTED] On Behalf Of Dan Hardy > > Sent: Wednesday, July 19, 2006 1:31 PM > > To: [email protected] > > Subject: Problem consuming Remedy web services using Axis > > > > > > ** > > > > I'm accessing Remedy web services for the first time, and running > > into an error. > > > > I'm using Java/Axis as the client, and I generated the client stubs > > using WSDL2Java. This gives me two classes (one for submitting > > requests, one for modifying requests), based on two WSDL files. > > > > When my code makes a request of either service, providing values for > > all parameters, I get an error like the below error - it seems the > > error always complains about the first element being missing. This > > looks to me like the request is definitely getting to the AR Server, > > and it is rejecting the content. > > > > Any clues? Are Remedy web services compatible with Axis clients? I > > google'd and found a couple of other people that have hit this > > problem, but no solutions posted. > > > > Thanks, > > Dan > > > > > > MessageType: 2 > > > > MessageNum: 8961 > > > > MessageText: Required element expected in the input XML document > > > > AppendedText: <businessUnit> ________________________________________________________________________ _______ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
