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 - 179 - Type Compatibility in Assignment of EPRs


I believe this is a duplicate of issue 51. 51 calls for us to fix the 
assignment rules once and for all. I think that is preferable then 
trying to fix them bit by bit.

	Just my two cents,

		Yaron

ws-bpel issues list editor wrote:
> This issue has been added to the wsbpel issue list with a status of "received". 
> The status will be changed to "open" if the TC accepts it as identifying a bug 
> in the spec or decides it should be accepted specially. Otherwise it will be 
> closed without further consideration (but will be marked as "Revisitable")
> 
> The issues list is posted as a Technical Committee document to the OASIS WSBPEL 
> TC pages <http://www.oasis-open.org/apps/org/workgroup/wsbpel> 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 
> <http://www.oasis-open.org/apps/org/workgroup/wsbpel/documents.php> - 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 <http://www.choreology.com/external/WS_BPEL_issues_list.html>.
> 
> 
>     Issue - 179 - Type Compatibility in Assignment of EPRs
> 
> *Status:* received
> *Date added:* 12 Nov 2004
> *Categories:* Data handling <#category_data_handling>
> *Date submitted:* 12 November 2004
> *Submitter:* Dieter Koenig <mailto:dieterkoenig@de.ibm.com>
> *Document:* Specification working draft, Section 9.3.1, "Type Compatibility in 
> Assignment".
> *Description:* In Section 9.3.1, the second list bullet reads:
> 
>     The from-spec is a variable of a WSDL message type and the to-spec is not,
>     or vice versa. This is not legal because parts of variables, selections of
>     variable parts, or endpoint references cannot be assigned to/from variables
>     of WSDL message types directly. 
> 
> One could interpret this as if an assignment from a variable of a WSDL message 
> type to a partner link is not allowed because the partner link is not itself a 
> variable of a WSDL message type. Likewise for assignments in the reverse direction.
> *Submitter's proposal:* Clarify that an assignment to/from a partner link IS 
> allowed when the from/to spec is a variable of a WSDL message type.
> 
> The endpoint reference is in a message part of this WSDL message, either the 
> complete part or an element contained in the part.
> *Changes:* 12 Nov 2004 - new issue
> 
> --------------------------------------------------------------------------------
> 
> To comment on this issue (including whether it should be accepted), please 
> follow-up to this announcement on the wsbpel@lists.oasis-open.org list (replying 
> to this message should automatically send your message to that list), or ensure 
> the subject line as you send it *starts* "Issue - 179 - [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 - 179 - 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).
> 
> 
> Choreology Anti virus scan completed
> 


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