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 13 - Updated Proposed Resolution - propertyAlias query usage


+1

> -----Original Message-----
> From: Chris Keller [mailto:chris.keller@active-endpoints.com]
> Sent: Tuesday, February 03, 2004 6:49 AM
> To: 'rkhalaf'; wsbpel@lists.oasis-open.org
> Subject: RE: [wsbpel] Issue 13 - Updated Proposed Resolution -
> propertyAlias query usage
>
>
> Another place that an XPath expression is used with no way to override
> the expression language is in the propertyAlias extension element for
> WSDL.  The proposal should be modified to include propertyAlias query
> usage.  Below is the proposed change for propertyAlias.
>
> Current syntax:
>
> <wsbp:propertyAlias propertyName="QName" messageType="QName"
> part="NCName" query="queryString"/>
>
> Proposed Syntax:
>
> <wsbp:propertyAlias propertyName="QName" messageType="QName"
> part="NCName">
>   <wsbp:query queryLanguage=".."?> ?      query goes here
>   </wsbp:query>
> </wsbp:propertyAlias>
>
> Note: If the queryLanguage element is omitted it is assumed
> to be XPath
> 1.0.
>
> -----Original Message-----
> From: rkhalaf [mailto:rkhalaf@watson.ibm.com]
> Sent: Wednesday, December 10, 2003 11:41 AM
> To: wsbpel@lists.oasis-open.org
> Subject: [wsbpel] Issue 13 - Updated Proposed Resolution]
>
>   The proposal is to replace things with expressions and
> queries  from
> being an attribute to being an element. This would affect
> <from>, <to> ,
>
> <propertyAlias>, and conditions.  This would gear up for using other
> languages for querying that may have a structured syntax. An
> example is
> the upcoming XQueryX, a proposal for XQuery using XML syntax.
>   The case
>
> for string queries is also shown below.
>
> With elements instead of attributes, we can allow one to override the
> default query/expression languages locally. The proposal allows for
> optional query/expressionLanguage attributes on queries and
> conditions
> that can locally override the global default.
>
> Current syntax:
>
> <wsbp:from variable="ncname" part="ncname"? query="queryString"?/>
>
> <wsbp:link ... transitionCondition="..." />
> <wsbp:targets joinCondition="...">
> .. the same for switch's case, and the whileCondition
>
> Proposed syntax
>
> <wsbp:from variable="ncname" part="ncname"?>
>   <wsbp:query queryLanguage=".."?> ?      query goes here
>   </wsbp:query>
> </wsbp:from>
>
> For example, an XPath 1.0 query would be encoded:
>
> <wsbp:from variable="ncname" part="ncname"?>
>   <wsbp:query>
>   /shipNotice/ShipNoticeHeader/shipOrderID
>   </wsbp:query>
> </wsbp:from>
>
> Conditions:
>
> <wsbp:source ... >
>       <wsbp:transitionCondition
> expressionLanguage=".."?>...</transitionCondition>?
> </wsbp:source>
>
> and
>
> <wsbp:targets>
>     <wsbp:joinCondition
> expressionLanguage="..."?>...</joinCondition> ?
>      <wsbp:link.... />
> </wsbp:targets>
>
> .. the same for switch's case, and the whileCondition
>
> his mailing list (and be removed from the roster of the OASIS
> TC), go to
> http://www.oasis-open.org/apps/org/workgroup/wsbpel/members/le
ave_workgr
oup.php.



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_workgr
oup.php.





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]