You are viewing a plain text version of this content. The canonical link for it is here.
Posted to user@ode.apache.org by dawg <zo...@gmail.com> on 2009/11/13 18:59:39 UTC
Strange selectionFailure in assign activity
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.
Re: Strange selectionFailure in assign activity
Posted by Greg Lucas <gr...@gmail.com>.
Sorry - ignore what I said, I wasn't looking at the right WSDLs. :-)
<from variable="input" part="name"/>
<to>$SayHelloIn.parameters/name</to>
The to-spec here specifies a 'name' element that has not been initialized
yet, i.e. you are assigning text content to an element that doesn't exist.
You could initialize it by copying from a literal first.
~Greg
On Fri, 13 Nov 2009 17:04:46 -0500, dawg <zo...@gmail.com> wrote:
>
> Hi Greg,
>
> Not sure what you're suggesting is wrong with the assignment.
>
> If you're suggesting to replace:
>
> <assign name="Assign1">
> <copy>
> <from variable="input" part="name"/>
> <to>$SayHelloIn.parameters/name</to>
> </copy>
> </assign>
>
> with:
>
> <assign name="Assign1">
> <copy>
> <from variable="input" part="name"/>
> <to>$SayHelloIn.name</to>
> </copy>
> </assign>
>
> it doesn't seem right (and does not compile), but it does seem a bit
> strange
> when I compare it to previous processes I worked with. I'll have another
> look at it. I attach the wsdl of the service I'm calling so you can see
> the
> definition of SayHello.
>
> http://old.nabble.com/file/p26344276/HelloService.wsdl HelloService.wsdl
>
> Thanks,
> Dawg
>
>
>
> Greg Lucas-3 wrote:
>>
>> Your to/from seem wrong. Try
>>
>> <to>$SayHelloIn.name</to>
>>
>> in the first assign and
>>
>> <from>$SayHelloOut.greeting</from>
>>
>> in the second.
>>
>> On Fri, 13 Nov 2009 12:59:39 -0500, dawg <zo...@gmail.com>
>> 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>
>>>
>>
>>
>> --
>> Greg Lucas
>>
>>
>
--
Greg Lucas
Re: Strange selectionFailure in assign activity
Posted by dawg <zo...@gmail.com>.
Hi Greg,
Not sure what you're suggesting is wrong with the assignment.
If you're suggesting to replace:
<assign name="Assign1">
<copy>
<from variable="input" part="name"/>
<to>$SayHelloIn.parameters/name</to>
</copy>
</assign>
with:
<assign name="Assign1">
<copy>
<from variable="input" part="name"/>
<to>$SayHelloIn.name</to>
</copy>
</assign>
it doesn't seem right (and does not compile), but it does seem a bit strange
when I compare it to previous processes I worked with. I'll have another
look at it. I attach the wsdl of the service I'm calling so you can see the
definition of SayHello.
http://old.nabble.com/file/p26344276/HelloService.wsdl HelloService.wsdl
Thanks,
Dawg
Greg Lucas-3 wrote:
>
> Your to/from seem wrong. Try
>
> <to>$SayHelloIn.name</to>
>
> in the first assign and
>
> <from>$SayHelloOut.greeting</from>
>
> in the second.
>
> On Fri, 13 Nov 2009 12:59:39 -0500, dawg <zo...@gmail.com> 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>
>>
>
>
> --
> Greg Lucas
>
>
--
View this message in context: http://old.nabble.com/Strange-selectionFailure-in-assign-activity-tp26340705p26344276.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Strange selectionFailure in assign activity
Posted by Greg Lucas <gr...@gmail.com>.
Your to/from seem wrong. Try
<to>$SayHelloIn.name</to>
in the first assign and
<from>$SayHelloOut.greeting</from>
in the second.
On Fri, 13 Nov 2009 12:59:39 -0500, dawg <zo...@gmail.com> 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>
>
--
Greg Lucas
Re: Strange selectionFailure in assign activity
Posted by Greg Lucas <gr...@gmail.com>.
I haven't tried this, but see: http://ode.apache.org/flexible-assigns.html
Just be aware that relying on implicit initialization makes your BPEL
process less portable, since it is not defined by the spec.
~Greg
On Sat, 14 Nov 2009 11:21:11 -0500, dawg <zo...@gmail.com> wrote:
>
> Finally!!!!
>
> Thanks a million for ending my misery :)
>
> I'm really not sure it's "learning BPEL". Implicit initialisation seems
> natural, and since other BPEL engine (at least Sun's one) support it,
> and it
> simplifies the life of the service composer I wonder why ODE doesn't have
> it. I think this lack of implicit initialization and more importantly of
> accurate error reporting is a problematic and can be time consuming.
>
> Really appreciate the help.
>
> Thanks,
> Zohar
>
>
> Tammo van Lessen wrote:
>>
>> Hi,
>>
>> the "name" element should be in the null namespace, shouldn't it. Would
>> you give the following snippet a try?
>>
>> <svc1:sayHello xmlns:svc1="http://j2ee.netbeans.org/wsdl/HelloService">
>> <name xmlns=""/>
>> </svc1:sayHello>
>>
>> dawg wrote:
>>>>>
>>>>> This is so annoying! I'm wasting so much time on NOTHING!
>>>>>
>>
>> I'd rather saying you're investing time in learning BPEL :)
>>
>> Best,
>> Tammo
>>
>>
>
--
Greg Lucas
Re: Strange selectionFailure in assign activity
Posted by dawg <zo...@gmail.com>.
Finally!!!!
Thanks a million for ending my misery :)
I'm really not sure it's "learning BPEL". Implicit initialisation seems
natural, and since other BPEL engine (at least Sun's one) support it, and it
simplifies the life of the service composer I wonder why ODE doesn't have
it. I think this lack of implicit initialization and more importantly of
accurate error reporting is a problematic and can be time consuming.
Really appreciate the help.
Thanks,
Zohar
Tammo van Lessen wrote:
>
> Hi,
>
> the "name" element should be in the null namespace, shouldn't it. Would
> you give the following snippet a try?
>
> <svc1:sayHello xmlns:svc1="http://j2ee.netbeans.org/wsdl/HelloService">
> <name xmlns=""/>
> </svc1:sayHello>
>
> dawg wrote:
>>>>
>>>> This is so annoying! I'm wasting so much time on NOTHING!
>>>>
>
> I'd rather saying you're investing time in learning BPEL :)
>
> Best,
> Tammo
>
>
--
View this message in context: http://old.nabble.com/Strange-selectionFailure-in-assign-activity-tp26340705p26351412.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Strange selectionFailure in assign activity
Posted by Tammo van Lessen <tv...@gmail.com>.
Hi,
the "name" element should be in the null namespace, shouldn't it. Would
you give the following snippet a try?
<svc1:sayHello xmlns:svc1="http://j2ee.netbeans.org/wsdl/HelloService">
<name xmlns=""/>
</svc1:sayHello>
dawg wrote:
>>>
>>> This is so annoying! I'm wasting so much time on NOTHING!
>>>
I'd rather saying you're investing time in learning BPEL :)
Best,
Tammo
Re: Re: Re: Strange selectionFailure in assign activity
Posted by dawg <zo...@gmail.com>.
Hi Wenfeng,
I'm sorry for the bother, but still nothing seems to help.
I changed per your instructions below, and still it fails in Assign1.
This is the schema as I changed it:
<xs:element name="sayHello">
<xs:complexType>
<xs:sequence>
<xs:element name="name" type="xs:string" minOccurs="0">
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
<xs:element name="sayHelloResponse">
<xs:complexType>
<xs:sequence>
<xs:element name="return" type="xs:string" minOccurs="0">
</xs:element>
</xs:sequence>
</xs:complexType>
</xs:element>
and here's assign4, with added namespace prefix although I suspect this is
not what you meant.
<assign name="Assign4">
<copy>
<from>
<literal>
<svc1:sayHello
xmlns:svc1="http://j2ee.netbeans.org/wsdl/HelloService">
<svc1:name/>
</svc1:sayHello>
</literal>
</from>
<to>$SayHelloIn.parameters</to>
</copy>
</assign>
Still the failure is in Assign 1 that tries to take the input and copy to
name.
I really appreciate your help.
Thanks,
Dawg
ZHAO Wenfeng wrote:
>
> Hello dawg,
>
> Two possible issues:
> 1) The schema might require the names of all elements, including "name"
> in "sayHello", be qualified, please check it. If true, add the prefix to
> "name" in the <from-spec> section.
>
> 2) Change your schema about "sayHello" from named complexType to named
> element, as the schema in my previous mail.
>
>
> Wenfeng
>
> =======On 2009-11-14 at 20:00:00 dawg wrote: =======
>
>>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.
>>
>>.
>
> = = = = = = = = = = = = = = = = = = = =
> ZHAO Wenfeng (赵文峰)
> Ph.D. Candidate
> http://www.bupt.edu.cn
>
>
>
--
View this message in context: http://old.nabble.com/Strange-selectionFailure-in-assign-activity-tp26340705p26351111.html
Sent from the Apache Ode User mailing list archive at Nabble.com.
Re: Strange selectionFailure in assign activity
Posted by dawg <zo...@gmail.com>.
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.
Re: Re: Strange selectionFailure in assign activity
Posted by dawg <zo...@gmail.com>.
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.