ode-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Pishava <pish...@yahoo.com>
Subject Re: Initializing Varibales in BPEL script?
Date Tue, 23 Jun 2009 17:03:23 GMT
Thanks. Yes  you are right. But my problem is that if I don't initialize the input variable
"foo" in <receive variable="foo" ..../> example, I will get the 
Assignment Fault exception. For example in my case I get this error:
: {http://docs.oasis-open.org/wsbpel/2.0/process/executable}selectionFailure,lineNo=132,faultExplanation=R-Value
expression "{OXPath10Expression $input.payload/ns1:RoomID_25__}" did not select any nodes.

While If I initialize it after "receive" activity, I will not get this error. Maybe something
is wrong somewhere else, but I don't know what and where?

Do you have any idea?

--- On Tue, 6/23/09, Matthieu Riou <matthieu.riou@gmail.com> wrote:

From: Matthieu Riou <matthieu.riou@gmail.com>
Subject: Re: Initializing Varibales in BPEL script?
To: user@ode.apache.org
Date: Tuesday, June 23, 2009, 7:45 PM

On Mon, Jun 22, 2009 at 9:04 AM, Pishava <pishava@yahoo.com> wrote:

> Hello,
>  Is it necessary to initialize all variables  defined in BEPL script prior
> using them in  Service Invocation?
> Because my BPEL script throws AssignmentFault exception when a variable is
> not initialized prior to mapping to its content to another variables.
> There is no problem in intializing all variables, but how  about  the
> "Input" mesage variable of the Process itself?!! I can jsut initialize it
> after "first receive" activity, which creates BPEL instance. In that case I
> will lost the "actual" input values for the process.
> Any idea, comment?

Input variables are initialized in full using your message so they are
initialized from the message and you shouldn't need to set them to anything.
So if you have the following:

<receive variable="foo" ..../>

The foo variable will be set to the content of your message when it arrives.


> regards,
> /shahab

  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message