Hi guys! I have a problem. The operation is used as the request element name instead of the name specified in the WSDL. Let me explain further:
I'm trying to consume a webservice with a Set Fields action and I have a WSDL which I can access. When I load this WSDL in my Set Fields action, I get to choose a webservice: "BPELprocessSubUnits" and an operation: "process". Then I set up the mappings and save. The WSDL defines a request element, something like <BPELsubUnitsProcessRequest>. However, when I consume the webservice, I see that <process>, not <BPELsubUnitsProcessRequest> is placed in the soap body!!! I'm using Remedy Administrator 6.3 patch 024, and the server has the same version and patch level. What can be causing this? It's doing my head in... -- View this message in context: http://www.nabble.com/Wrong-request-element-for-consuming-webservice-%28ARS-6.3%29-tp19308789p19308789.html Sent from the ARS (Action Request System) mailing list archive at Nabble.com. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
