RE: [uddi-spec] Proposed Agenda Item - affecting CR 002

[Tom Bellwood <bellwood@us.ibm.com>]

So sorry!   I've annotated the note below, identifying the new piece
between <tab></tab> markers.


Thanks,
Tom Bellwood       Phone:  (512) 838-9957 (external);   TL:  678/9957
(internal)
Co-Chair, OASIS UDDI Specification TC
STSM - Emerging Technologies
IBM Corporation

"Von Riegen, Claus" <claus.von.riegen@sap.com> on 04/30/2003 03:20:12 AM

To:    Tom Bellwood/Austin/IBM@IBMUS, uddi-spec@lists.oasis-open.org
cc:
Subject:    RE: [uddi-spec] Proposed Agenda Item - affecting CR 002



Tom,

Which part of the text was in red and what is the issue?

Claus

-----Original Message-----
From: Tom Bellwood [mailto:bellwood@us.ibm.com]
Sent: Montag, 28. April 2003 22:19
To: uddi-spec@lists.oasis-open.org
Subject: [uddi-spec] Proposed Agenda Item - affecting CR 002






We've found what looks like another minor typo in the V3 spec.   See
attached for details.  I would propose that this item be added to the list
for CR 002 on typos.   Luc - please add to the next agenda.

Thanks,
Tom Bellwood       Phone:  (512) 838-9957 (external);   TL:  678/9957
(internal)
Co-Chair, OASIS UDDI Specification TC

---------------------- Forwarded by Tom Bellwood/Austin/IBM on 04/28/2003
03:16 PM ---------------------------

From:  Richard B Allen on 04/28/2003 11:05 AM

To:    Tom Bellwood/Austin/IBM
cc:    Anh Lu/Austin/IBM
Subject:


Tom,

It looks like the V3 spec incorrectly copied the caveats across all
delete_xxx API's. The text in red should not apply to delete_tModel since
tModels may be deleted (hidden) multiple times.

5.2.11.4 Caveats:
If an error occurs in processing this API call, a dispositionReport element
MUST be returned to the caller within a SOAP Fault. See Section 4.8 Success
and Error Reporting. In addition to the errors common to all APIs, the
following error information is relevant
here:
* E_invalidKeyPassed: Signifies that one of the uddiKey values passed did
not match with any known tModelKey values
</tab>or multiple instances of the same tModelKey values were passed.</tab>
The invalid key references SHOULD be clearly indicated in the error text.

This was identified when a defect was returned. Currently our code rejects
multiple deletes of same tModel in one call.

Rick Allen
Lotus Notes: Richard B Allen/Austin/IBM@IBMUS
Internet: rballen@us.ibm.com
(512) 838-3786,  t/l 678-3786