How to define message without parts in WSDL?

Question

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?

Answer 1

Hi again,
Srin, you were right. I did have a namespace issue. Getting that resolved however, introduced a new error.
My BPEL process invokes the remote partner, delivers the payload, the remote partner sends back a meaningful response, but no BPEL instance is shown in the BPEL console.
In the <oracle home>/opmn/logs I find the following errors:
ORABPEL-05002
Message handle error.
An exception occurred while attempting to process the message "com.collaxa.cube.engine.dispatch.message.invoke.InvokeInstanceMessage"; the exception is: Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "java.lang.NullPointerException
And
Exception: java.lang.NullPointerException
Handled As: com.collaxa.cube.CubeException
+] -> [java.lang.NullPointerException: null]+
ORABPEL-00000
Exception not handled by the Collaxa Cube system.
An unhandled exception has been thrown in the Collaxa Cube system. The exception reported is: "java.lang.NullPointerException
This seems strange to me. It seems that even if the meaningfull answer from the partner link is lost enroute I should still get a response in BPEL (maybe just null). My next step will be to try and set up a TCP Monitor between the partnerlink server and the BPEL server.
Any thoughts, hints, ideas and solutions are very welcome.
Will report on progress
Regard,
Aagaard
Edited by: Aagaard on Oct 10, 2008 10:18 AM
Update:
My current thinking is that I have a problem with my message types. The problem is definitely in the way BPEL handles the response from the partnerlink. The nullpointer exception may suggest that I am trying to assign the return payload to an incompatible type. I don't know if it could be an issue if the partnerlink response is some specific type while I excpect a string?
Anyway here's what my wsdl looks like now:
<?xml version="1.0" encoding="UTF-8"?>
<definitions name="RCMR_AR000002NR01"
targetNamespace="http://com.scandihealth.ccs.webservices.messaging.common/CCSMessageServiceRemote.wsdl"
xmlns="http://schemas.xmlsoap.org/wsdl/"
xmlns:tns="http://com.scandihealth.ccs.webservices.messaging.common/CCSMessageServiceRemote.wsdl"
xmlns:xsd="http://www.w3.org/2001/XMLSchema"
xmlns:soap="http://schemas.xmlsoap.org/wsdl/soap/" >
<documentation>
WSDL for Service: CCSMessageServiceRemote, generated by Oracle WSDL toolkit (version: 1.1)
</documentation>
<types>
<schema targetNamespace="http://schemas.xmlsoap.org/wsdl/" xmlns:tns="http://com.scandihealth.ccs.webservices.messaging.common/CCSMessageServiceRemote.xsd" xmlns="http://www.w3.org/2001/XMLSchema" xmlns:xsd="http://www.w3.org/2001/XMLSchema">
<element name="msgInputOutput" type="xsd:string"/>
</schema>
</types>
<message name="RCMR_IN000002NR01InputOutput">
<part name="param0" element="msgInputOutput"/>
</message>
<portType name="CCSMessageServiceRemotePortType">
<operation name="RCMR_IN000002NR01">
<input message="tns:RCMR_IN000002NR01InputOutput"/>
<output message="tns:RCMR_IN000002NR01InputOutput"/>
</operation>
</portType>
<binding name="CCSMessageServiceRemoteBinding" type="tns:CCSMessageServiceRemotePortType">
<soap:binding transport="http://schemas.xmlsoap.org/soap/http" style="rpc"/>
<operation name="RCMR_IN000002NR01">
<soap:operation soapAction="urn:com-scandihealth-ccs-webservices-messaging-common-CCSMessageServiceRemote/RCMR_IN000002NR01"/>
<input>
<soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/literal/" namespace="urn:com-scandihealth-ccs-webservices-messaging-common-CCSMessageServiceRemote" />
</input>
<output>
<soap:body use="literal" encodingStyle="http://schemas.xmlsoap.org/soap/literal/" namespace="urn:com-scandihealth-ccs-webservices-messaging-common-CCSMessageServiceRemote"/>
</output>
</operation>
</binding>
<service name="CCSMessageServiceRemote">
<port name="CCSMessageServiceRemotePort" binding="tns:CCSMessageServiceRemoteBinding">
<soap:address location="http://.../HL7Receive_servlet_WS/WS"/>
</port>
</service>
</definitions>
My assignment / invokation looks like this:
<assign name="CreateInputParamGenerateMessage">
<copy>
<from variable="getContentAsString"/>
<to variable="RCMR_IN000002NR01Input" part="param0"/>
</copy>
</assign>
<invoke name="InsertOperation"
partnerLink="RCMR_AR000002NR01"
portType="ns6:CCSMessageServiceRemotePortType"
operation="RCMR_IN000002NR01"
inputVariable="RCMR_IN000002NR01Input"
outputVariable="RCMR_IN000002NR01Output"/>