I think Fred is right on the mark. FWIW: I think the reason that the order (which is just one part of the structure) of the XML is checked before the filters are invoked is that the WebService must first parse the XML, and the parser is doing it in a "normal" XML WSDL based way. This error is generated by the web server component of the path to the ARS server and not from the ARS server itself. While I have not tested it I would imagine that this error is even thrown before the user credentials are checked against the ARS server. So I doubt the ARS server ever sees any traffic from a "malformed XML document".
-- Carey Matthew Black Remedy Skilled Professional (RSP) ARS = Action Request System(Remedy) Love, then teach Solution = People + Process + Tools Fast, Accurate, Cheap.... Pick two. On 5/24/07, Grooms, Frederick W <[EMAIL PROTECTED]> wrote:
** Brand is in the data? Is it in the correct position in the XML data? I have noticed with Web Services if you specify a field in the form as Required that you have to have it in the inbound XML data (even if you have defined a filter to populate it on Submit). Apparently the Required field checks are executed before the Filters are run. Fred ________________________________ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Frank Caruso Sent: Thursday, May 24, 2007 4:24 PM To: arslist@ARSLIST.ORG Subject: Re: SOAP OpSet ** I would agree but I continually get the following type of error and I've tried a few different ways of submitting teh Set request: Fault : MessageType: 2 MessageNum: 8961 MessageText: Required element expected in the input XML document AppendedText: <Brand> Faultcode :soapenv:Server.userException Faultdetail : Brand is getting set in the Data section. Any further insight on why this error would appear?
_______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org ARSlist:"Where the Answers Are"
