RE: Update

[Honorez Dylan <Dy...@cronos.be>]

Hi Stephen,

I tried to find this in your bug database, but couldn't find it. Is the
bug still there, or did you resolve it? If it hasn't been resolved yet,
I'll take a look at it.

Kind regards,
Dylan Honorez,
dylan.honorez@cronos.be
 
-----Original Message-----
From: Viens, Stephen [mailto:Stephen.Viens@LibertyMutual.com] 
Sent: vrijdag 1 oktober 2004 20:25
To: juddi-user@ws.apache.org
Subject: RE: Update

I'll take a look at it this weekend and see if I can at least commit a
fix.  Not sure when a 0.9 final will be available yet ... I've been
waiting a bit for bugs to come in (this one would have been
significant).

Steve

-----Original Message-----
From: Honorez Dylan [mailto:Dylan.Honorez@cronos.be] 
Sent: Friday, October 01, 2004 10:27 AM
To: juddi-user@ws.apache.org
Subject: RE: Update


Ok Steve.

I just fixed it then by deleting the tmodel, removing the key from the
tmodel and saving the tmodel as a new one.

The issue then is of course that I get a new key, which is certainly not
what we aim for, but will have to do in the meanwhile.

When are you planning on releasing the final version 0.9? 

Kind regards,
Dylan Honorez,
dylan.honorez@cronos.be
 

-----Original Message-----
From: Viens, Stephen [mailto:Stephen.Viens@LibertyMutual.com] 
Sent: vrijdag 1 oktober 2004 16:12
To: juddi-user@ws.apache.org
Subject: RE: Update

Okay, definitely a bug then.

The UDDI spec says that you never actually 'delete' a tModel but rather
mark it as deleted.  What's happening in the case of the save_tModel  is
that jUDDI is marking the tModel as deleted but never actually removing
it from the Database.  Then when jUDDI tries to save (insert) the DB
throws a "duplicate key" message because an entry with that key is still
in the DB.

This won't be fixed until the 0.9 final release is available.

Steve

-----Original Message-----
From: Honorez Dylan [mailto:Dylan.Honorez@cronos.be] 
Sent: Friday, October 01, 2004 10:01 AM
To: juddi-user@ws.apache.org
Subject: RE: Update


Steve,

When I perform a delete_tmodel just before saving the updated tmodel, I
get this error when saving:

The uuid_key value passed did not match with any known key values.

Met vriendelijke groeten,
Dylan Honorez,
dylan.honorez@cronos.be
 

-----Original Message-----
From: Viens, Stephen [mailto:Stephen.Viens@LibertyMutual.com] 
Sent: vrijdag 1 oktober 2004 15:26
To: juddi-user@ws.apache.org
Subject: RE: Update

Honorez, that sounds like a bug.  

Try issuing a delete_tModel before saving.  

Steve

-----Original Message-----
From: Honorez Dylan [mailto:Dylan.Honorez@cronos.be] 
Sent: Friday, October 01, 2004 9:20 AM
To: juddi-user@ws.apache.org
Subject: RE: Update


Steve, 

When I fetch the tModel object, edit the overviewURL and try to save it
I get:

Invalid argument value,  message from server: "Duplicate entry
'uuid:57ECCE20-13AC-11D9-8E20-FD1418594377' for key 1"

Kind regards,
Dylan Honorez,
dylan.honorez@cronos.be
 
-----Original Message-----
From: Viens, Stephen [mailto:Stephen.Viens@LibertyMutual.com] 
Sent: vrijdag 1 oktober 2004 14:54
To: juddi-user@ws.apache.org
Subject: RE: Update

Updating is done through UDDI's save_xxx functions. 

Per the UDDI specification if you perform any save_xxx function and a
key is present in the object you're saving then (business_key,
service_key, binding_key or tModel_key) then an update (delete then
insert) of the entire object occurs.

If no key is present then an "insert" type of operation is assumed and a
the UDDI node with generate a key for the object and return it to you.

Steve

-----Original Message-----
From: Honorez Dylan [mailto:Dylan.Honorez@cronos.be] 
Sent: Friday, October 01, 2004 4:41 AM
To: juddi-user@ws.apache.org
Subject: Update


Hi,

Is updating possible within juddi? 
Or do I have to get the object with api, delete it from juddi, update it
with api and submit it again?

Kind regards,
Dylan Honorez,
dylan.honorez@cronos.be
http://www.xt-i.com