https://stackoverflow.com/questions/19627966
italiano
english
français
española
中国
日本の
العربية
Deutsch
한국어
Português
RussianWelcome to the wild world of XML namespaces. Take a seat, it's not pretty.
Very important: XML namespaces look like URLs but they're not web-page addresses. They're just unique strings, for which the standard web-URL-looking-thing seems to work quite well.
Basically, every element in an XML file, which includes both the BPEL file and your input file is assigned to a namespace. These are defined in a bunch of ways, which include assigning a default namespace (a targetNamespace) in an enclosing element, and definining namespace with abbreviations that then get prefixed to the element name to give a full definition.
So at the top of your BPEL file, in the actual <bpel:process tag, you define XML namespace ns0 like this: xmlns:ns0="http://ws.wso2.org/dataservice".
So when you specify the fields to look for in your BPEL in the copy / from element like this:
<ns0:op1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ns0:NID/>
<ns0:Name/>
</ns0:op1>
It's looking for elements op1, NID and Name elements to be in the http://ws.wso2.org/dataservice namespace.
But that's actually
- Wrong, according to the WSDL that applies (see below)
- Not what you've supplied in your XML file (or at least in the XML posted above).
Because you're using a tool to get the input, fixing point 1. will probably (possibly?) fix point 2.
If we break down what you're trying to do and what XML is calculating:
You're calling the CreateAccount operation (line 37)
<bpel:receive name="Receive" partnerLink="AOPPL" operation="CreateAccount" portType="ns:AccountOpeningProcessService" variable="AOPPLRequest" createInstance="yes"/>
So it's looking for a variable that's called AOPPLRequest. That's defined above (line 22): <bpel:variable name="AOPPLRequest" messageType="ns:CreateAccountRequest"/>
That says it's going to be of type CreateAccountRequest in the namespace that is defined with the ns prefix.
The ns prefix is defined in line 1 also: xmlns:ns="http://wso2.org/banking" -
Important: this is the actual namespace you should be supplying and looking for in your copy command.
I'd actually like to find what the valid structures for a CreateAccountRequest message is.
Line 10 says this: <bpel:import namespace="http://wso2.org/banking" location="AccountOpeningProcessService.wsdl" importType="http://schemas.xmlsoap.org/wsdl/"/>
This is good because a WSDL file is used to define web-services. Google helps here, so I googled AccountOpeningProcessService.wsdl and got a link into the wso2 svn repository, which is good enough for me: https://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/docs/src/main/resources/samples/banking-sample/Webinar/AccountOpeningProcess/ And theres a link to the WSDL file I want from there. https://svn.wso2.org/repos/wso2/trunk/tools/ide/eclipse/docs/src/main/resources/samples/banking-sample/Webinar/AccountOpeningProcess/AccountOpeningProcessService.wsdl
That WSDL file includes this gem:
<xsd:schema targetNamespace="http://wso2.org/banking">
<xsd:element name="CreateAccount">
<xsd:complexType>
<xsd:sequence>
<xsd:element name="nid" type="xsd:string" />
<xsd:element name="name" type="xsd:string"></xsd:element>
<xsd:element name="accountType" type="xsd:string"></xsd:element>
</xsd:sequence>
</xsd:complexType>
</xsd:element>
Note that targetNamespace is there, which basically means "if I don't give you a namespace, then use this one as a default", so everything defined here is in the namespace http://wso2.org/banking
This is good because that's the namespace we identified previously in line 22, referring to the element in line 37.
What that means, is that this fragment of your copy structure (from line 71) appears to be the problem:
<bpel:assign validate="no" name="InitCustomerDataserviceRequest">
<bpel:copy>
<bpel:from>
<bpel:literal xml:space="preserve">
<ns0:op1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ns0:NID/>
<ns0:Name/>
</ns0:op1>
</bpel:literal>
</bpel:from>
It's looking for elements in the namespace http://ws.wso2.org/dataservice (ns0 as defined in the first line), instead of the namespace http://wso2.org/banking, which is ns as defined in the first line.
So I'd suggest (without having access to wso2), you find a way to change that copy from element to this:
<bpel:assign validate="no" name="InitCustomerDataserviceRequest">
<bpel:copy>
<bpel:from>
<bpel:literal xml:space="preserve">
<ns:op1 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
<ns:NID/>
<ns:Name/>
</ns:op1>
</bpel:literal>
</bpel:from>
That is change ns0: to ns: - thereby putting them into the correct namespace.
Unfortunately, this mismatch between the two namespaces is throughout your BPEL, so I think you're in for a long battle.
I've found (specifically with JCAPS, anyway) that once the namespaces get mangled like this, it's sometimes quicker to create the BPEL again from scratch.
