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] assign query without part?




Hi,

I see what you guys mean now. I overlooked "the entire part" phrase from the spec. 
"with '/' meaning the root of the document fragment representing the entire part"

That phrase is probably problematic for non-WSDL msg variables. That phrase or that sentence or even that paragraph may need to be refined for variables based on XSD-Qualified-Type or XSD-Qualified-Element.

We may want to have a clear "switch-case" statement in the spec: (something like)
----------------------------
if the variable is declared based on a WSDL 1.1 message type, both part and query are applicable.
if the variable is declared based on a XSD-qualified-element, query is applicable but part is not applicable.
if the variable is declared based on a XSD-qualified-type (simple type or complex type), query is not applicable.
When the query language is an XPath, it MUST always start with '/', which means the root of the document which contains the corresponding entire part of a WSDL message variable or the XSD qualified-element variable.
----------------------------

[Actually, IMHO, a BPEL declared based on a XSD complex type (as opposed to a XSD qualified element) is ill-defined. We may want to make it illegal explicitly in BPEL spec for clarity.]


Thanks!



Regards,
Alex Yiu




Muruga Chinnananchi wrote:
I am particularly concerned about these sentences in section 14.3.

"For XPath 1.0, the value of the query attribute MUST be an absolute
locationPath (with '/' meaning the root of the document fragment
representing the entire part). It is used to identify the root of a
subtree within the document fragment representing the part".

After reading this I am thinking that you can't have query without part.

But there is no "part" for element variables. So for element variables, we
should allow query attribute without part attribute. In this is true, I
suggest that we should change the content to:

"For XPath 1.0, the value of the query attribute MUST be an absolute
locationPath (with '/' meaning the root of the document fragment). It is
used to identify the root of a subtree within the document fragment".

thanks,
-muruga
-----Original Message-----
From: Muruga Chinnananchi [mailto:muruga@collaxa.com]
Sent: Sunday, March 07, 2004 8:47 PM
To: wsbpel@lists.oasis-open.org
Subject: [wsbpel] assign query without part?


Confusion about assign.
Spec section 14.3 says the following (see below).

"In the first from-spec and to-spec variants of assignment, an optional
query attribute may be used in executable processes, yielding the forms

 <from variable="ncname" part="ncname"? query="queryString"?/>
<to variable="ncname" part="ncname"? query="queryString"?/>

For XPath 1.0, the value of the query attribute MUST be an absolute
locationPath (with '/' meaning the root of the document fragment
representing the entire part). It is used to identify the root of a
subtree within the document fragment representing the part".

The question is:

For <to>, is it allowed to have "query" without "part"?. If it is not
allowed to have "query" without "part" then I would suggest to remove the
"?" for part, like below.
<from variable="ncname" part="ncname" query="queryString"?/>
<to variable="ncname" part="ncname" query="queryString"?/>

I have an element variable which doesn't have "part" and I want to use that
element variable in <to>. How do i  use element variables in <to>?

thanks,
-muruga


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.





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]