juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Edward Benson (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] Commented: (JUDDI-37) Updating an existing tModel fails, and causes it to be removed from registry
Date Fri, 28 Jan 2005 02:24:17 GMT
     [ http://issues.apache.org/jira/browse/JUDDI-37?page=comments#action_58199 ]
     
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 UDDI4J.
>     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"
> xmlns="urn:uddi-org:api_v2"><authInfo>authToken:34EEDA90-EC05-11D8-9A90-
> 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"
> tModelKey="uuid:8609C81E-EE1F-4D5A-B202-3EB13AD01823"/></identifierBag><
> 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:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


Mime
View raw message