OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

wsbpel message

[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]


Subject: Re: [wsbpel] Issue - 11 - Ambiguous insertion points


ah, i see your point now.  if i might paraphrase, you can initialize an
uninitialized variable, provided you init the whole thing.  (it doesn't
matter what you're initializing *from*).  i think that's the appropriate
distinction.  if that's what you're saying, then yes, i agree.

danny

----- Original Message ----- 
From: "Edwin Khodabakchian" <edwink@collaxa.com>
To: "'Danny van der Rijn'" <dannyv@tibco.com>; <wsbpel@lists.oasis-open.org>
Cc: "'Muruga Chinnananchi'" <muruga@collaxa.com>; "'Glenn Mi'"
<gmi@collaxa.com>; <ygoland@bea.com>
Sent: Wednesday, August 06, 2003 2:09 PM
Subject: RE: [wsbpel] Issue - 11 - Ambiguous insertion points


> Danny,
>
> I am not arguing about the lack of insertion (and transformation) support
in
> BPEL. I am just trying to create a distinction between initialisation of
an
> XML variable and the insertion of an element to an existing variable. The
> first one can be achieved through copy of XML literal representation (see
> example). The second requires XPATH function or service call outs.
>
> Example
> -----------------------------
> <assign>
>    <copy>
>       <from>
>          <StockReviewSheet xmlns="http://samples.cxdn.com/finance">
>             <Symbol></Symbol>
>             <TargetPrice>0.0</TargetPrice>
>             <CurrentPrice>0.0</CurrentPrice>
>             <Action></Action>
>             <Quantity>0</Quantity>
>          </StockReviewSheet>
>       </from>
> <to variable="someVariable" />
>     </copy>
> </assign>
>
> May be we should consider adding <assign>/<insert> and <assign>/<tranform>
> instead of overloading <assign>/<copy>
>
> Edwin
>
>
> > -----Original Message-----
> > From: Danny van der Rijn [mailto:dannyv@tibco.com]
> > Sent: Wednesday, August 06, 2003 1:30 PM
> > To: wsbpel@lists.oasis-open.org
> > Cc: 'Muruga Chinnananchi'; 'Glenn Mi'; ygoland@bea.com
> > Subject: Re: [wsbpel] Issue - 11 - Ambiguous insertion points
> >
> > no, it can't.  there's no current way to address an insertion
> > point for said initialization in a currently uninitialized
> > variable.  that's what this discussion is about.  it's hard
> > to grasp (at least it was hard for me) that this "feature"
> > doesn't exist in BPEL 1.1, but due to limitations (which
> > yaron has done a good job of introducing us to), receiving a
> > message is the only way to get data into BPEL.
> >
> > IMO, this is one of the most serious defects in the current
> > spec, and fixing it won't be trivial.  apologies for my
> > simplistic proposal - it wasn't meant to be anything more
> > than a very flimsy strawman, and i should have explained that earlier.
> >
> > danny
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: wsbpel-unsubscribe@lists.oasis-open.org
> For additional commands, e-mail: wsbpel-help@lists.oasis-open.org
>
>




[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]