[ http://issues.apache.org/jira/browse/JUDDI-54?page=history ]
Steve Viens resolved JUDDI-54:
------------------------------
Resolution: Fixed
This was also an issue for bindingKeys when saving a Service (via saveService).
The fix has been applied in both places.
The recommended fix has been applied.
> 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
> Assignee: 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/JDBCDataStore.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
