[jira] [Resolved] (JUDDI-891) revise juddi install data to match the root node id per spec
[ https://issues.apache.org/jira/browse/JUDDI-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree resolved JUDDI-891. -- Resolution: Fixed > revise juddi install data to match the root node id per spec > > > Key: JUDDI-891 > URL: https://issues.apache.org/jira/browse/JUDDI-891 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3 > > > i noted today that the spec states that the node id must equal the root > business id. so we'll have to update the default install data. > we should also add a check for at seed time, to at least log a warning about > the mismatch. I don't see how it's really a big deal though and it probably > won't interfere with even the replication engine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (JUDDI-891) revise juddi install data to match the root node id per spec
[ https://issues.apache.org/jira/browse/JUDDI-891?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Alex O'Ree resolved JUDDI-891. -- Resolution: Fixed > revise juddi install data to match the root node id per spec > > > Key: JUDDI-891 > URL: https://issues.apache.org/jira/browse/JUDDI-891 > Project: jUDDI > Issue Type: Bug > Components: core >Reporter: Alex O'Ree >Assignee: Alex O'Ree > Fix For: 3.3 > > > i noted today that the spec states that the node id must equal the root > business id. so we'll have to update the default install data. > we should also add a check for at seed time, to at least log a warning about > the mismatch. I don't see how it's really a big deal though and it probably > won't interfere with even the replication engine. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
