juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Viens, Stephen" <Stephen.Vi...@LibertyMutual.com>
Subject RE: [jira] Commented: (JUDDI-37) Updating an existing tModel fails, and causes it to be removed from registry
Date Fri, 28 Jan 2005 03:18:20 GMT
Ed, let me take a closer look. I believe this should be fixed but I
because 0.9rc3 was released before the fix was applied it hasn't made it
into a new release yet.  An 0.9rc4 (or better a 0.9 final) is overdue.


-----Original Message-----
From: Edward Benson (JIRA) [mailto:juddi-dev@ws.apache.org] 
Sent: Thursday, January 27, 2005 9:24 PM
To: juddi-dev@ws.apache.org
Subject: [jira] Commented: (JUDDI-37) Updating an existing tModel fails,
and causes it to be removed from registry

Edward Benson commented on JUDDI-37:

Is this issue fixed? I am running jUDDI 0.9rc3 on Tomcat 4.1.31 with
mySQL and when I try to update a tModel it marks the old tModel as
deleted in the database and then never does the update (thus returning a
null result). Subsequent attempts to read that UUID fail. 

> Updating an existing tModel fails, and causes it to be removed from 
> registry
>          Key: JUDDI-37
>          URL: http://issues.apache.org/jira/browse/JUDDI-37
>      Project: jUDDI
>         Type: Bug
>  Environment: JUDDI 0.9rc3 running on Tomcat 5.0.  Client is using
>     Reporter: Alex Holmes
>     Assignee: Steve Viens
>      Fix For: 0.9

> When I try and update an existing tModel with new data, I get an 
> exception that complains of a duplicate key (which is true, as I'm 
> updating, not creating a new one).  However, then the tModel that I 
> tried updating can't be retrieved at all from the registry.
> Here's the request and response messages:
> Request body:
> <save_tModel generic="2.0"
> 9E70B848F48B</authInfo><tModel
> authorizedName="John Doe" operator="jUDDI.org"
> tModelKey="uuid:D5B01E30-EB5B-11D8-9E30-FE99729CEBA3"><name>Alex's
> tmodel</name><overviewDoc/><identifierBag><keyedReference keyName="aa"
> keyValue="cc"
> categoryBag/></tModel></save_tModel>
> Response body:
> <Fault><faultstring>Duplicate key or integrity constraint violation, 
> message from server: &quot;Duplicate entry
> 'uuid:D5B01E30-EB5B-11D8-9E30-FE99729CEBA3' for key
> 1&quot;</faultstring></Fault>

This message is automatically generated by JIRA.
If you think it was sent incorrectly contact one of the administrators:
If you want more information on JIRA, or have a bug to report see:

View raw message