Re: [wsbpel] Issue - 139.1 - Proposal For Vote

["Yaron Y. Goland" <ygoland@bea.com>]

I need to change the BNF as you specified.

Static analysis in this case is a very blunt technique because for it to 
be useful it would have to be pessimistic which I think is going too 
far. We already have a fault for calling an un-initialized partnerLink, 
I suspect we should leave it at that.

		Yaron


Chris Keller wrote:
> Hi Yaron,
> 
> Is the "may" in your xml syntax correct? If so its behavior is not defined.
> Also the initializePartnerRole should be optional according to your text.
> So should the proposed syntax be:
> 
> <partnerLinks>
>       <partnerLink name="ncname" partnerLinkType="qname"
>            myRole="ncname"? partnerRole="ncname"?
>            initializePartnerRole="yes|no"? /> +
> </partnerLinks>
> 
> 
> Question:
> 
> In the case of "no" should static analysis detect the case that no
> assignment was made to the partnerLink?  Or are there other ways that we
> think the process itself (not the infrastructure) can initialize the
> partnerLink?
> 
> - Chris
> 
> -----Original Message-----
> From: Yaron Y. Goland [mailto:ygoland@bea.com]
> Sent: Wednesday, June 22, 2005 4:41 PM
> To: wsbpeltc
> Subject: [wsbpel] Issue - 139.1 - Proposal For Vote
> 
> Issue 139.1: How/when BPEL can change partner role EPR
> 
> Proposal: Put in a switch to specify if the programmer is depending on
> the BPEL processor to initialize a partnerRole value on a partnerLink.
> This switch has no affect on the engine's behavior after the partnerLink
> is used for the first time.
> 
> Section 7.2
> 
> Change the BNF to read:
> 
> <partnerLinks>
>       <partnerLink name="ncname" partnerLinkType="qname"
>            myRole="ncname"? partnerRole="ncname"?
>            initializePartnerRole="yes|no|may">+
>       </partnerLink>
> </partnerLinks>
> 
> From: In the degenerate case where a partnerLinkType has only one role,
> one of these attributes is omitted as appropriate.
> 
> To: In the case where a WSDL binding is only specified for one of the
> two roles then one of these attributes is omitted as appropriate.
> 
> Insert the following as a new paragraph after the paragraph that ends
> with " See Assignment for the mechanisms used for dynamic assignment of
> endpoint references to partner services."
> 
> The initializePartnerRole attribute specifies if the BPEL processor is
> required to initialize a partnerLink's partnerRole value. The attribute
> has no affect on the partnerRole's value after its initialization. The
> initializePartnerRole attribute MUST NOT be used on a partnerLink that
> does not have a partner role; this restriction MUST be statically enforced.
> 
> If the initializePartnerRole attribute is set to "yes" then the BPEL
> processor MUST initialize the EPR for the specified
> partnerLink/partnerRole combination before that partnerRole is first
> referenced by the BPEL process.
> 
> If the initializePartnerRole attribute is set to "no" then the BPEL
> processor MUST NOT initialize the EPR for the specified
> partnerLink/partnerRole combination before that partnerRole is first
> referenced by the BPEL process.
> 
> If the initializePartnerRole attribute is omitted then its value MUST be
> treated as "no".
> 
> 
> 
> ---------------------------------------------------------------------
> To unsubscribe from this mail list, you must leave the OASIS TC that
> generates this mail.  You may a link to this group and all your TCs in OASIS
> at:
> https://www.oasis-open.org/apps/org/workgroup/portal/my_workgroups.php
> 
> 
> 
> 
>