Re: [ws-tx] Issue 037: incomplete resolution

[Alastair Green <alastair.green@choreology.com>]

Andy, Ian, Mark --

You're quite right. The WD does remove the row, in line with the agreed 
resolution, and includes the textual statement.

Apologies for setting this hare running.

Alastair

Mark Little wrote:
> +1
>
> On 14 Aug 2006, at 13:43, Andrew Wilkinson3 wrote:
>
>> Apologies for not posting sooner to nip this in the bud.
>>
>> I believe that the latest working draft
>> (http://www.oasis-open.org/apps/org/workgroup/ws-tx/download.php/19308/wstx-wsat-1.1-spec-wd-08.pdf) 
>>
>> has executed the resolution of the issue in full. Alasdair's original
>> e-mail points to incorrect entries in the register row of the CV state
>> table however, in wd-08, this row is no longer present. Wd-08 also
>> contains the additional text in 4.3.1.
>>
>> The only thing that remains is the editorial tweak to ensure consistency
>> in referring to and the naming of faults (the name's should be space
>> delimited); this will be applied in due course as agreed on last week's
>> telecon.
>>
>> Thanks,
>> Andy
>>
>>
>>
>>
>> Ian Robinson/UK/IBM@IBMGB
>> 11/08/2006 07:11
>>
>> To
>> "Monica J. Martin" <Monica.Martin@Sun.COM>, Andrew
>> Wilkinson3/UK/IBM@IBMGB, mark.little@jboss.com
>> cc
>> Alastair Green <alastair.green@choreology.com>, 
>> Monica.Martin@Sun.COM, Ram
>> Jeyaraman <Ram.Jeyaraman@microsoft.com>, ws-tx@lists.oasis-open.org
>> Subject
>> Re: [ws-tx] Issue 037: incomplete resolution
>>
>>
>>
>>
>>
>>
>> The resolution to the issue included the removal of the 2
>> Register/RegisterResponse rows from the 2PC state table. Precisely, the
>> approved resolution was as described in Alastair's amendment note:
>> http://lists.oasis-open.org/archives/ws-tx/200606/msg00078.html
>>
>> In summary:
>> 1. Remove the 2 Register/RegisterResponse rows from the 2PC state 
>> tables.
>> 2. Augment the text in section 4.3.1 so that we do not lose any
>> information
>> as a result of removing these rows. Agreed text:
>> "Further participants may register with the coordinator until the
>> coordinator issues a Prepare to any durable participant. Once this has
>> happened the Registration Service for the coordinator MUST respond to 
>> any
>> further Register request with a Cannot Register Participant fault
>> message".
>>
>> Can the AT spec editors please ensure this resolution is executed in 
>> full.
>>
>> Regards,
>> Ian Robinson
>> STSM, WebSphere Transactions Architect
>> IBM Hursley Lab, UK
>>
>>
>>
>>              "Monica J.
>>              Martin"
>>              
>> <Monica.Martin@Su                                          To
>>
>>              n.COM>                    Ram Jeyaraman
>>              Sent by:                  <Ram.Jeyaraman@microsoft.com>
>>              
>> Monica.Martin@Sun                                          cc
>>
>>              .COM                      Alastair Green
>>                                        <alastair.green@choreology.com>,
>>                                        ws-tx@lists.oasis-open.org
>>              10/08/2006 18:00                                      
>> Subject
>>
>>                                        Re: [ws-tx] Issue 037: incomplete
>>                                        resolution
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>
>>> jeyaraman: Yes, the proposed change seems fine.
>>>
>>> The CV table row Register, columns { Preparing, PreparedSuccess,
>>> Committing, Aborting }: Replace "Invalid State" with "Cannot Register
>>> Participant".
>>>
>>> The space delimited form "Cannot Register Participant" is better.
>>>
>>>
>> mm1: Do we need to reopen this issue or create another one to address?
>> Maybe just bring it up on next conference call to expedite change. 
>> Thanks.
>>
>>> -----Original Message-----
>>> From: Alastair Green [mailto:alastair.green@choreology.com]
>>> Sent: Friday, July 28, 2006 7:53 AM
>>> To: ws-tx@lists.oasis-open.org
>>> Subject: [ws-tx] Issue 037: incomplete resolution
>>>
>>> Issue 037 was resolved by agreeing that any late registration will
>>> receive Cannot Register Participant in response.
>>>
>>> However, the CV state table shows Invalid State being sent when late
>>> (post-prepare wave) registrations occur.
>>>
>>> Proposal: to ask the editors to amend the cells in the CV Register row
>>> that show Invalid State and replace with CannotRegisterParticipant.
>>>
>>> Secondary, stylistic issue. Do we name faults in the form XYZ or X Y Z?
>>> Example: "CannotRegisterParticipant" or "Cannot Register Participant".
>>>
>>> Resolutions of 037 and of 050 use different forms. Suggest we always 
>>> use
>>> space delimited form, as this is the pattern elsewhere.
>>>
>>> Alastair
>>>
>>>
>>
>>
>>
>>
>>
>>
>
>