BPEL Process transporting problem.from 10.1.2. to 10.1.3(SOA)

Question

Hi,
When i move the project to new SOASuite designer, the transformation activity is showing as assign activity.. and its not moving the imported xsd folders from project root folder to the bpel folder.So while building, it's not able to find the xsd in the relative path what is there in the wsdl.
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.