BPEL process fails in SOA (in UNIX), but works fine in SOA (in Windows) env

Question

Hello,
BPEL process fails in SOA (in UNIX), but works fine in SOA (in Windows) environment
Step 1: Build a asynchronous BPEL process which has no extra node. Make and deploy it in 'local windows desktop SOA' server
The BPEL process has three nodes:
a. client - on the left side of the swim lane
b. receiveInput - first node in swim lane (client calls 'receiveInput')
c. callbackClient - second and last node in the swim lane ('callbackClient' calls client)
Step 2: Go to BPEL console and 'Initiate' the BPEL process -> 'Post XML Message'
Step 3: Now, I can see the successfully completed BPEL instance in the BPEL console.
Now,
Step 4: Deploy the same BPEL process (dummy asynchronous) in the SOA server (hosted in unix box)
Step 5: Go to BPEL console and 'Initiate' the BPEL process -> 'Post XML Message'
Step 6: I find that the BPEL instance appears to have ended in error (on the second node i.e. callbackClient )
With the following error message
+<invalidVariables xmlns="http://schemas.oracle.com/bpel/extension"><part name="code"><code>9710</code>+
+</part><part name="summary"><summary>Invalid xml document.+
According to the xml schemas, the xml document is invalid. The reason is: Error::cvc-complex-type.2.4.b: The content of element 'DummyBPELProcessProcessResponse' is not complete. One of '{"http://xmlns.oracle.com/DummyBPELProcess":result}' is expected.
Please make sure that the xml document is valid against your schemas.
+</summary>+
+</part></invalidVariables>+
Has anyone faced similar issue as above ?
i.e. process works find in windows environment (local SOA), but fails in SOA server in UNIX environment
Appreciate your help in understanding this issue.
Thanks,
Santhosh

Answer 1

Hello,
The fix to this issue appears to have been as follows:
+<schema attributeFormDefault="unqualified"+
+     elementFormDefault="qualified"+
+     targetNamespace="http://xmlns.oracle.com/DummyBPELProcess"+
+     xmlns="http://www.w3.org/2001/XMLSchema">+
+     <element name="DummyBPELProcessProcessRequest">+
+          <complexType>+
+               <sequence>+
+                    <element name="input" type="string"/>+
+               </sequence>+
+          </complexType>+
+     </element>+
+     <element name="DummyBPELProcessProcessResponse">+
+          <complexType>+
+               <sequence>+
+                    <element name="*:result*" type="string"/>+
+               </sequence>+
+          </complexType>+
+     </element>+
+</schema>+
In DummyBPELProcess.xsd,
modifiying "result" to ":result" appears to have resolved the issue in SOA under unix environment.
If anyone can explain why "result" works in SOA under windows and ":result" works in SOA under unix environment, I would really appreciate your help.
Thanks,
Santhosh