[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]
Subject: subject lines and issues list (was RE: [wsbpel] Issue 229 - Proposal for vote)
Please don't send messages with a Subject line that leaves you as Issue xyz - Propos... because my scripts perceive that to be a new proposal and I have to intervene stop them changing the status. Not a big deal, just a convenience. The Re: in a follow-up messages prevents this. And the scripts ignore all the [wsbpel] etc. Peter > -----Original Message----- > From: aalves@bea.com [mailto:aalves@bea.com] > Sent: 05 January 2006 17:29 > To: alex.yiu@oracle.com > Cc: arkin@intalio.com; wsbpel@lists.oasis-open.org; > chris.keller@active-endpoints.com > Subject: [wsbpel] Issue 229 - Proposal for vote > > > Hi, > > This is a minor observation, but I don't find it that > confusing to differentiate between <compensate/> and > <compensate scope="X"/>. > > I actually think it makes sense to have the same Xml element > relate to both forms of compensation, as, after-all, both do > deal with compensation of their inner scopes, the latter > selectively. > > Compensation is a tricky feature to explain nonetheless, it > seems to me that having a more descriptive name won't help > that much, hence I am in favor of keeping the simplicity of > the single compensate name. > > For example, we don't have a <receiveInOnly/>, > <receiveInOut/> instead of just <receive/>. Also > <compensateInner/> seems to indicate that there is a > <compensateOuter/>. > > Anyway, just my opinion, either way we go is fine with me. > > Sincerely, >
[Date Prev] | [Thread Prev] | [Thread Next] | [Date Next] -- [Date Index] | [Thread Index] | [List Home]