Issue - 305 - Remove query language in favor of expression language for <to>

This issue has been added to the wsbpel issue list with a status of "received".
The status will be changed to "open" if a motion to open the issue is proposed and that
motion is approved by the TC. A motion could also be proposed to close it without
further consideration. Otherwise it will remain as "received".

The issues list is posted as a Technical Committee document to the 
OASIS WSBPEL TC pages
on a regular basis. The current edition, as a TC document, is the most recent version of 
the document entitled  in the 
"Issues" folder of the WSBPEL TC document list
- the next posting as a TC document will include this issue.
The list editor's working copy, which will normally include an issue when it is announced, is available at 
this constant URL.

Issue - 305 - Remove query language in favor of expression language for <to>
Status: received

Date added: 21 Jul 2006

Date submitted: 21 July 2006

Submitter: Chris Keller

Description: In the BPEL 1.1 spec queries had a context. The context for the query was either provided by the propertyAlias or a copy operation component (<from> or <to>). The differences between expressions and queries in 1.1 was clear – queries had a context and expressions did not.

This has changed in the WS-BPEL 2.0 spec. Queries still have a context when used as part of propertyAlias but not as part of a copy operation component. Other than the separate configuration of a query language there is no discernable difference between queries and expressions in a WS-BPEL 2.0 process so why have both?

The proposal includes the following changes:

remove queryLanguage from <process>

replace queryLanguage in <to> with expressionLanguage

The propertyAlias will retain its queryLanguage since it provides a context for the query to execute. 

Changes: 21 Jul 2006 - new issue

To comment on this issue (including whether it should be accepted), please follow-up to this announcement on the 
 list (replying to this message should automatically send your message to that list), or ensure
the subject line as you send it starts "Issue - 305 - [anything]" or is a reply
to such a message. If you want to formally propose a resolution to an open issue, please start the subject line 
"Issue - 305 - Proposed resolution", without any Re: or similar.

To add a new issue, 
see the issues procedures document (but the address for new issue submission is the sender of this announcement).