Hi ZHAO, thanks for your help.
I'm really getting desperate with it.
I added the initialization (as I understand it) which passes just to fail in
assign1. Same failure - selection failure.
<xs:complexType name="sayHello">
<xs:sequence>
<xs:element name="name" type="xs:string" minOccurs="0">
</xs:element>
</xs:sequence>
</xs:complexType>
<xs:complexType name="sayHelloResponse">
<xs:sequence>
<xs:element name="return" type="xs:string" minOccurs="0">
</xs:element>
</xs:sequence>
</xs:complexType>
<variables>
<variable name="SayHelloOut"
xmlns:tns="http://j2ee.netbeans.org/wsdl/HelloService";
messageType="tns:sayHelloResponse"/>
<variable name="SayHelloIn"
xmlns:tns="http://j2ee.netbeans.org/wsdl/HelloService";
messageType="tns:sayHello"/>
<variable name="output"
xmlns:tns="http://j2ee.netbeans.org/wsdl/HelloWSDL";
messageType="tns:HelloWSDLOperationResponse"/>
<variable name="input"
xmlns:tns="http://j2ee.netbeans.org/wsdl/HelloWSDL";
messageType="tns:HelloWSDLOperationRequest"/>
</variables>
<assign name="Assign4">
<copy>
<from>
<literal>
<sayHello>
<name/>
</sayHello>
</literal>
</from>
<to>$SayHelloIn.parameters</to>
</copy>
<copy>
<from>
<literal>
<sayHelloResponse>
<return/>
</sayHelloResponse>
</literal>
</from>
<to>$SayHelloOut.parameters</to>
</copy>
</assign>
<assign name="Assign1">
<copy>
<from variable="input" part="name"/>
<to>$SayHelloIn.parameters/name</to>
</copy>
</assign>
Do you see a problem with that?
This is so annoying! I'm wasting so much time on NOTHING!
Thanks,
Dawg
ZHAO Wenfeng wrote:
>
> Hello dawg,
>
> What I suggested is same with Greg. A historical thread in this mail
> list
> has clarified how to intialize variables in ODE:
> http://old.nabble.com/Must-BPEL-complex-variable-initialization-use-extension-mechanisms--tc22904186.html#a22904186
>
>
> In short, we should "initialize the entire target variable using the
> complete element in the literal from-spec"
>
> For example, given the declaration of the variables:
> <variables xmlns:ws0="http://example.com/service01.wsdl";>
> ... ...
> <variable name="_a" element="ws0:elemA" />
> <variable name="_b" element="ws0:elemB" />
> <variable name="_c" element="ws0:elemC" />
> <variable name="_a2" element="ws0:elemA2" />
> </variables>
> and the schema:
> <schema targetNamespace="http://example.com/service01.wsdl";
> xmlns="http://www.w3.org/2001/XMLSchema";
> elementFormDefault="qualified">
> ... ...
> <element name="ResultInfo">
> <complexType>
> <sequence>
> <element name="elemA">
> <complexType>
> <sequence>
> <element name="elemB">
> <complexType>
> <sequence>
> <element name="elemC"
> type="string" maxOccurs="unbounded"/>
> </sequence>
> </complexType>
> </element>
> </sequence>
> </complexType>
> </element>
> <element name="elemA2" type="string"/>
> </sequence>
> </complexType>
> </element>
> </schema>
>
> We should initialize $_b as:
> <copy>
> <from><literal>
> <svc01:elemB xmlns:svc01="http://example.com/service01.wsdl";>
> <svc01:elemC/>
> </svc01:elemB>
> </literal></from>
> <to>$_b</to>
> </copy>
> Then we are permitted to copy some values to $_b or its child.
>
>
> Hope it helpful to you.
>
> Wenfeng
>
> =======On 2009-11-14 at 15:55:09 dawg wrote: =======
>
>>Thanks ZHAO,
>>
>>So I need to explicitly initialize the variables I'm using except those
used
>>in receive, but what is the format for initialization. Everything I try
>>failed - tried to initialized with an empty string literal, tried what you
>>suggested below (although I don't understand what it's doing and seems to
>>copy between incompatible types) and nothing worked. Could you please
>>clarify what kind of initialization is needed?
>>
>>Thanks,
>>Dawg
>>
>>
>>ZHAO Wenfeng wrote:
>>>
>>> Hello dawg,
>>>
>>> Although the HelloService.wsdl isn't given out by you, I think the
>>> problem with you is that in ODE a variable need be initialized by hand,
>>> except it is used in <receive> where it is intialized by default and
>>> assigned to values at same time.
>>> Taking your first assignment as example, you can try to insert another
>>> <copy> before it:
>>> <copy>
>>> <from>
>>> <literal>
>>> <name/>
>>> </literal>
>>> </from>
>>> <to>$SayHelloIn.parameters</to>
>>> </copy>
>>>
>>> For more details, see
>>> http://old.nabble.com/ODE-selectionFault-tc25460550.html#a25464370
>>>
>>> Wenfeng
>>>
>>> =======On 2009-11-14 at 01:59:39 dawg wrote: =======
>>>
>>>>
>>>>Hi,
>>>>
>>>>I have this simple BPEL process attached. It's really simple! when I
>>invoke
>>>>it using SoapUI I'm getting this selectionFailure on the assign
activity.
>>>>
>>>>I attach the BPEL and the WSDL files and the corresponding tomcat log.
>>>>
>>>>http://old.nabble.com/file/p26340705/HelloWSDL.wsdl HelloWSDL.wsdl
>>>>http://old.nabble.com/file/p26340705/HelloBPELProcess.bpel
>>>>HelloBPELProcess.bpel
>>>>http://old.nabble.com/file/p26340705/log.rtf log.rtf
>>>>
>>>>This is the SOAP input:
>>>>
>>>><soapenv:Envelope
>>xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/";
>>>>xmlns:hel="http://j2ee.netbeans.org/wsdl/HelloWSDL";>
>>>> <soapenv:Header/>
>>>> <soapenv:Body>
>>>> <hel:HelloWSDLOperation>
>>>> <name>joe</name>
>>>> </hel:HelloWSDLOperation>
>>>> </soapenv:Body>
>>>></soapenv:Envelope>
>>>>
>>>>
>>>>Thanks,
>>>>Dawg
>>>>
>>>>--
>>>>View this message in context:
>>http://old.nabble.com/Strange-selectionFailure-in-assign-activity-tp26340705p26340705.html
>>>>Sent from the Apache Ode User mailing list archive at Nabble.com.
>>>>
>>>
>>> = = = = = = = = = = = = = = = = = = = =
>>> ZHAO Wenfeng (赵文峰)
>>> Ph.D. Candidate
>>> http://www.bupt.edu.cn
>>>
>>>
>>>
>>
>>--
>>View this message in context:
http://old.nabble.com/Strange-selectionFailure-in-assign-activity-tp26340705p26347956.html
>>Sent from the Apache Ode User mailing list archive at Nabble.com.
>
> = = = = = = = = = = = = = = = = = = = =
> ZHAO Wenfeng (赵文峰)
> Ph.D. Candidate
> http://www.bupt.edu.cn
>
>
>
--
View this message in context:
http://old.nabble.com/Strange-selectionFailure-in-assign-activity-tp26340705p26349433.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
