On Feb 11, 2005, at 10:08 AM, Anil Saldhana wrote:
Geir, I had thought of the same a month back.
I thing the right thing to do is call jUDDI n times for n keys to delete, because we have to keep track of partial commits.
Right - OTOH, the JavaDoc says
"partial commits are allowed"
not required. I figure that we do want to try the one-shot first, and if that fails, then iterate through... I'll add that as a JIRA in Scout-land. (Will give me a reason to go find it...)
geir
Regards, Anil
--- Geir Magnusson Jr <[EMAIL PROTECTED]> wrote:
Additional thought...
On Feb 11, 2005, at 6:58 AM, Geir Magnusson Jr. wrote:and have a partial
JAXR says that I can do a deleteOrganizations()commit, stopping on the first failure. In mycase, I assume that thefirst good key will be deleted, and the secondnot. This seems thenthat to use jUDDI (or any UDDI registry - I'm notpicking on jUDDI), Imust send two separate delete_business messages?
... if I wish to perform partial commits? seems like the performant thing to do is assume that this kind of failure is rare, always try single-message multi-key deletes, returning a JAXR BulkResponse to my callers w/ only one error in the event of a failure, letting them assume that nothing worked?
How does a UDDI user figure out which key is bad since the UDDI response message doesn't give any hint of which key was the bad one...? Seems like you then need to play delete_business wack-a-mole...
geir
+1-203-665-6437
-- Geir Magnusson Jr[EMAIL PROTECTED]
-- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED]
__________________________________ Do you Yahoo!? Read only the mail you want - Yahoo! Mail SpamGuard. http://promotions.yahoo.com/new_mail
-- Geir Magnusson Jr +1-203-665-6437 [EMAIL PROTECTED]
