OASIS Mailing List ArchivesView the OASIS mailing list archive below
or browse/search using MarkMail.

 


Help: OASIS Mailing Lists Help | MarkMail Help

sca-bpel message

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


Subject: Re: [sca-bpel] [NEW ISSUE] Need to add Capability to indicate that aPartnerLink should be ignored when introspecting the ComponentType of aBPEL Process



Danny,

Sure, I have no problem with a better name.

@ignore sounds fine to me.

Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  mike_edwards@uk.ibm.com



From: Danny van der Rijn <dannyv@tibco.com>
To: Mike Edwards/UK/IBM@IBMGB
Cc: OASIS BPEL <sca-bpel@lists.oasis-open.org>
Date: 08/09/2009 18:13
Subject: Re: [sca-bpel] [NEW ISSUE] Need to add Capability to indicate that a PartnerLink should be ignored when introspecting the ComponentType of a BPEL Process





+1 to the issue.

-1 to the proposed name.  IMO it should be something like @notInComponentType - but shorter  ;-)  possibly @ignore.  @skip just doesn't sit right on my ear.

Mike Edwards wrote:


Raiser:                        Mike Edwards


Target:                        sca-bpel-1.1-spec-cd02.doc


Description:


Currently, any declaration of a partnerLink within a BPEL process results in a <service/> or a <reference/> appearing in the componentType of the

BPEL process.


This is not desirable in all circumstances:


- it may be that a BPEL process is written with an inner loop, where the inner loop is implemented as a nested <scope/>.  In this inner loop, it may

be that a partnerLink is declared within the nested scope and used purely as a "local variable" within the loop, for example where it is a reference
and the reference target/EPR is assigned to it from the contents of a variable held in an outer scope.


In these circumstances, the partnerLink in the inner loop is shadowing a partnerLink in the outer scope - logically it represents the same partnerLink

reference as the partnerLink in the outer scope.


At present, SCA cannot handle a situation such as this - the inner partnerLink is introspected as a <reference/> and so is the outer partnerLink - this

means 2 references appear when only one is called for.


To change this, it is necessary to provide a capability for the writer of a BPEL process to indicate that a given partnerLink should NOT be used

to introspect a <service/> or a <reference/> in the componentType.


Proposal:


Add a new SCA BPEL extension attribute that can be used to annotate a <partnerLink/> element.


@skip


boolean - default value is false


When @skip="true", the <partnerLink/> element is ignored when introspecting  the compoenntType of the BPEL Process.


The changes are shown in this marked up version of CD02, where the changes are in Section 3.3 and Appendix A.




Yours,  Mike.

Strategist - Emerging Technologies, SCA & SDO.
Co Chair OASIS SCA Assembly TC.
IBM Hursley Park, Mail Point 146, Winchester, SO21 2JN, Great Britain.
Phone & FAX: +44-1962-818014    Mobile: +44-7802-467431  
Email:  
mike_edwards@uk.ibm.com




Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU












Unless stated otherwise above:
IBM United Kingdom Limited - Registered in England and Wales with number 741598.
Registered office: PO Box 41, North Harbour, Portsmouth, Hampshire PO6 3AU








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