juddi-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Alex O'Ree (JIRA)" <juddi-...@ws.apache.org>
Subject [jira] [Commented] (JUDDI-734) Handle when a Node changes it ID
Date Thu, 13 Nov 2014 03:41:33 GMT

    [ https://issues.apache.org/jira/browse/JUDDI-734?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14209206#comment-14209206
] 

Alex O'Ree commented on JUDDI-734:
----------------------------------

Suggested procedure (via documentation):
-run a tool (or a new web service method) that will somehow halt all external requests.
-alter all the operational info fields in the database, changing the current node name, for
the new node name.
-once completed, shutdown juddi (or the container)
-update juddiv3.xml config file (perhaps manually)
-restart juddi

I don't see any other way around this. 


> Handle when a Node changes it ID
> --------------------------------
>
>                 Key: JUDDI-734
>                 URL: https://issues.apache.org/jira/browse/JUDDI-734
>             Project: jUDDI
>          Issue Type: Bug
>          Components: core, documentation
>            Reporter: Alex O'Ree
>            Assignee: Kurt T Stam
>             Fix For: 3.2.1
>
>
> We need to handle when an admin changes the node id by ripping through the database and
updating all of the entity records's node id field in order to prevent orphaned records that
can't be updated.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

Mime
View raw message