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 - 125 - Proposal for Vote


I suggest we hold off on resolving 125 until 103 and 51 are resolved. 
They deal with these same issues but in a larger context.
	Thanks,
		Yaron

andrew.francis@mail.mcgill.ca wrote:
> Hi Yuzo:
> 
>  > INCORRECT
>  >  <variable name="intTypeVar" type="xsd:int"/>
>  >  ...
>  >  <assign>
>  >    <copy>
>  >      <from>0</from>   <!-- INCORRECT -->
>  >      <to variable="intTypeVar"/>
>  >    </copy>
>  >  </assign>
> 
>  >CORRECT
>  >  <variable name="intTypeVar" type="xsd:int"/>
>  >  ...
>  >  <assign>
>  >    <copy>
>  >      <from><p:intVal xsi:type="xsd:int">0</p:intVal></from>
>  >      <to variable="intTypeVar"/>
>  >    </copy>
>  >  </assign>
> 
> Why is it so difficult for a BPEL parser to do the right
> thing in this example? The <from> has an attribute that
> specifies its "category" (i.e., variable). Absence impliesa literal. The 
> compiler looks at the category and type of
> the <to>, and sees if <from> is type compatible (or
> can be coerced into a compatible type). Perhaps if the
> parser is not sure what to do, it generates a warning.
> 
> Autoboxing springs to mind when I look at these
> two examples.
> 
> Cheers,
> Andrew
> 
> 
> 
> 
> To unsubscribe from this mailing list (and be removed from the roster of the 
> OASIS TC), go to 
> http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/leave_workgroup.php.
> 


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