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] [Updated] (JUDDI-707) Identify the purpose for UDDIClerk.saveNode(Node n) and a workflow of how its used
Date Thu, 13 Nov 2014 03:36:27 GMT

     [ https://issues.apache.org/jira/browse/JUDDI-707?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Alex O'Ree updated JUDDI-707:
-----------------------------
    Priority: Minor  (was: Critical)

> 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
>          Components: documentation, juddi-client
>            Reporter: Alex O'Ree
>            Assignee: Kurt T Stam
>            Priority: Minor
>             Fix For: 3.2.1
>
>
> 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.3.4#6332)

Mime
View raw message