BPEL Process migration problems from 10.1.2. to 10.1.3(SOA)

Question

Hi,
I am migrating the BPEL Project which was desinged for the BPEL(10.1.2) using BPEL Designer to SOA Suite using the JDeveloper 10.1.3.1 Developer Preview version.
The taken the project which is deploying&working perfectly in the BPEL Desg&serv (10.1.2).
But the same project is not compiling in the newer preview version.i got invalid xpath exception.
my xpath is like
bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input/ns1:listOfProducts')
if i change like this xpath, woking fine...
bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input')
The input element defined as string in wsdl.However am expecting in runtime process will recive an proper xml string as a value of input element so the xpath will work fine..
Is the any configuration property to turn of xpath validation & variable not initialized warning while compile and building bpel project in the jdevstudio10.1.3.1. preview as well as in SOASuite server.
I would be happy on any reply.
Thanks
bogi

Answer 1

Hi,
Bogiraja and me work on the same team... this is a follow up we noticed today. As part of the deployment descriptors of a BPEL, one can set the configuration property "xpathValidation" to False (it is by default True going by 10.1.2 documentation). The documentation says that this would make the compiler not to validate the xpath queries.
When we tried this in 10.1.3, it did not seem to make any difference and the compiler still did not allow a xpath query which contained a node name which was not defined in the WSDL (bpws:getVariableData('inputVariable','payload','/client:commonProjectProcessRequest/client:input/ns1:listOfProducts') in Bogiraja's mail above)
Basically, the problem is like this.
a. The WSDL for the BPEL process defines the input variable as a "string"
b. When this BPEL process is invoked, we read the content of this variable which is an XML and assign that to a variable of a defined type in the BPEL.
c. For this purpose, we used to use the syntax as mentioned by Bogiraja in 10.1.2 which does not seem to work on 10.1.3.
A further observation is that if we define a dummy variable of xsd:any and copy the content of the input into that variable and then apply a similar xpath ('/client:dummyXSDAnyVar/ns1:listOfProducts') on that resultant variable then it seems to work!!
Expected functionality? Anything we seem to be missing out here?
Would highly appreciate any responses.
Thanks in advance.