Hi all,
I don't know if it is possible, but I would like to create a message without defining part/type.
Really what I want to accomplish is to avoid the
part definition below in my .wsdl file.
...
<message name="RCMR_IN000002NR01Input">
<part name="param0" type="xsd:string"/>
</message>
<message name="RCMR_IN000002NR01Output">
<part name="param0" type="xsd:string"/>
</message>
...
So I would like to something akind to
...
<message name="RCMR_IN000002NR01Input">
</message>
<message name="RCMR_IN000002NR01Output">
</message>
...
I try to assign a string to RCMR_IN000002NR01Input (I am using rpc literal). At the moment the partnerlink receiving my message gets confused by the param0 part of the XML.
I hope that description of my issue was not to cryptic to be understandable. Please feel free to ask clarifying questions.
Any help is appreciated.
Regards,
Aagaard
Edited by: Aagaard on Oct 8, 2008 8:42 AM
Maybe I should try to elaborate on my use case.
I pick up a SOAP message from a JMS queue (well, topic really). The message is a domain specific type. I get the content of the message as a string and assign it to a variable with a param0 of type string.
I then use the contains function to determine which partnerlink to invoke for a given message.
The invokation is succesful seen from BPEL.
However, the receiving systems receives my message including the original SOAP envelope - AND including a new BPEL generated SOAP envelope :-(
This is addition to the following code which was the concern of my original post:
<part xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" name="param0">
<param0 xmlns="" xmlns:def="http://www.w3.org/2001/XMLSchema" xsi:type="def:string" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
So anybody have any ideas as to how to get rid of unnecessary SOAP envelope and that irritating param0?