Geir, Good catch. It occurred to me that this may have also been a problem with bindingKeys in the saveService method of JDBCDataStore and it was. I've applied the recommended fix to both the saveBusiness and saveService methods.
I've marked the issue as 'resolved' in JIRA. If you have a moment to confirm that the fix is working as you expect it to please let me know and I'll 'close' it. Thanks. Steve -----Original Message----- From: Geir Magnusson Jr (JIRA) [mailto:[EMAIL PROTECTED] Sent: Saturday, February 12, 2005 8:33 PM To: [email protected] Subject: [jira] Created: (JUDDI-54) When updating a business w/ a service, existing service key gets recreated When updating a business w/ a service, existing service key gets recreated ------------------------------------------------------------------------ -- Key: JUDDI-54 URL: http://issues.apache.org/jira/browse/JUDDI-54 Project: jUDDI Type: Bug Components: Apache Scout Requests Reporter: Geir Magnusson Jr Assigned to: Steve Viens If you have an exiting business (Organization in JAXR parlance) that has a service, and you make an update to that business using save_business, any service key gets overwritten with a new one. The fix seems to be : Index: JDBCDataStore.java =================================================================== RCS file: /home/cvspublic/ws-juddi/src/java/org/apache/juddi/datastore/jdbc/JDBCDa taStore.java,v retrieving revision 1.9 diff -r1.9 JDBCDataStore.java 460a461,467 > > String serviceKey = service.getServiceKey(); > > if ((serviceKey == null) || (serviceKey.length() == 0)) { > service.setServiceKey(uuidgen.uuidgen()); > } > 462d468 < service.setServiceKey(uuidgen.uuidgen()); -- 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
