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 241 - Proposal Discussion - allowing optionalexplicit declaration (?)


Title: RE: [wsbpel] Issue 241 - Proposal for Vote

Hi DK, Mark and others,

For rest of Issue 241 discussion, I am going to spilt into two email threads:
(a) Whether to allow optional explicit declaration and its implication to <forEach>
      (That is *this* email thread)
(b) Whether to remove messageType and element from <onEvent>


For (a): whether to allow optional explicit declaration:
this issue has been decided in our previous directional vote on Issue 241.
So, it could go either way: allow or disallow.

After listening to Mark's viewpoint, I tend to go with his preferences.

That is, to make our lives easier and make our spec simpler by disallowing explicit declaration of variables in the associated scope.

Please let me know the preferences from you guys soon. Because, I am going to update the proposal by this round of feedback soon [ i.e. this evening, if other oracle's internal P0 interrupt happens to me. :-) ]

Thanks!



Regards,
Alex Yiu



DK wrote:

This suggestion is related to 241 and 204.

For more consistency across event handlers and forEach, if we allow
variables to be declared in the EH's associated scope:

"For cross-reference redundancy and clarity, these variables referenced by
variable attribute or <fromPart> element may be optionally declared in the
associated scope explicitly. If explicitly declared, variable types used in
declaration MUST be exact matches of the correponding definitions in WSDL."

then it would make sense to allow the optional explicit declaration of a
counter variable (in a scope associated with forEach) as well.

Any opinion?

Kind Regards
DK


Mark Ford wrote:

There shouldn't be an explicit declaration of the message variable when the <fromPart> is used. Allowing this introduces the possibility of an error and is inconsistent with the use of <fromPart> elsewhere in the spec.

I think an explicit declaration within a scope of the forEach's counter variable is unnecessary. The name of the variable is determined by the counterName attribute and its type is always the same. I don't think that the explicit declaration of this variable adds any value.



Regards,
Alex Yiu



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