Alex O'Ree created JUDDI-707:
--------------------------------
Summary: Identify the purpose for UDDIClerk.saveNode(Node n) and a
workflow of how its used
Key: JUDDI-707
URL: https://issues.apache.org/jira/browse/JUDDI-707
Project: jUDDI
Issue Type: Task
Reporter: Alex O'Ree
Assignee: Kurt T Stam
Priority: Critical
Fix For: 3.2
Looking at the code, it appears as if the purpose for UDDIClerk.saveNode is to
tell the specified Node "n" that Node "n" exists and to store it in its own
database.
This doesn't make any sense. My assumption is that the purpose of SaveNode and
SaveClerk of the jUDDI API service is to enable and facilitate internode
communication (and other admin stuff). Thus the question, should this be
reworked so that it reads more like, "hey current node that I'm connected to,
there's another UDDI node over there and I want you to hook up with them". This
sort of implies some kind of federation or trust level.
There's literally no documentation on this, so documenting this is a subtask.
--
This message was sent by Atlassian JIRA
(v6.1#6144)
