[
https://issues.apache.org/jira/browse/JUDDI-736?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13837132#comment-13837132
]
Alex O'Ree edited comment on JUDDI-736 at 12/7/13 1:23 PM:
-----------------------------------------------------------
For a scenario where there was only one node in the registry, we could in
theory allow the change by only updating the database.
In the linked JUDDI-727, I added the validation rule to ensure that users can
only change records on the 'home' node, i.e. the node that currently has
custody.
So considering that the multi-node registry is well defined, we have a few
options for a single node registry.
Option A) Block all node id changes from the admin console (must be set at
first start time) (Note: this will not prevent changes to the config file!)
Side effect: if a node change is desired, the admin would have two options
A1) start a new instance of jUDDI + database, setup up replication,
transfer everything over, deprecate the old instance, then stop it.
A2) use the CLI Migration Tool
Option B) Allow the change, but only if in a single node configuration and just
alter the database as required.
was (Author: spyhunter99):
For a scenario where there was only one node in the registry, we could in
theory allow the change by only updating the database.
In the linked JUDDI-727, I added the validation rule to ensure that users can
only change records on the 'home' node, i.e. the node that currently has
custody.
So considering that the multi-node registry is well defined, we have a few
options for a single node registry.
Option A) Block all node id changes from the admin console (must be set at
first start time)
Side effect: if a node change is desired, the admin would have two options
A1) start a new instance of jUDDI + database, setup up replication,
transfer everything over, deprecate the old instance, then stop it.
A2) use the CLI Migration Tool
Option B) Allow the change, but only if in a single node configuration and just
alter the database as required.
> Identify if the UDDI specs allows for node id changes or rename
> ---------------------------------------------------------------
>
> Key: JUDDI-736
> URL: https://issues.apache.org/jira/browse/JUDDI-736
> Project: jUDDI
> Issue Type: Task
> Reporter: Alex O'Ree
> Assignee: Kurt T Stam
> Fix For: 3.2
>
>
--
This message was sent by Atlassian JIRA
(v6.1#6144)
