Hi Mark, The suggestion I am giving here is not related to Remedy but more related to SOAP Return Envelope testing.
Can you try to consume service outside of Remedy (i.e. through Java or Perl or C# web-service client) and then do a Set fields for "Status" through a $PROCESS$ calling your web-service client (in java you can package it as a JAR and call it)? You will need to parse specifically that field from SOAP Response and return it to the $PROCESS$. See if you can parse out specifically that field from SOAP Response without any errors. Thanks Chintan. --- On Mon, 2/28/11, Mark Milke <[email protected]> wrote: From: Mark Milke <[email protected]> Subject: ARERR [8959] The XML data type is not supported. <> To: [email protected] Date: Monday, February 28, 2011, 8:35 AM Hi Listers, I've build a SOAP Message Queue and I'm testing a web service with our partner. I'm testing in manual mode, i.e. I'm setting every message's status to Completed in order to initiate the comsumption of our partner's Web Service. While consuming a web service I'm getting the error mentioned in the title and I have no idea what is causing it. What's even more odd is, that is SOAP message arrives at the Web Service provider, just can't set my message to Completed because of the error. When I let an escalation run over it, it will fail I guess. The top of oddity is that when I redo the mapping in the filter, the error disappears for a few hours to return a few hours later. Do you guys have an idea how to track down the problem? Mark _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
