[
https://issues.apache.org/jira/browse/JUDDI-706?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14255336#comment-14255336
]
ASF subversion and git services commented on JUDDI-706:
-------------------------------------------------------
Commit 43efbe4d12def6bc1420435d46739f3f23afa2ca in juddi's branch
refs/heads/master from [~spyhunter99]
[ https://git-wip-us.apache.org/repos/asf?p=juddi.git;h=43efbe4 ]
JUDDI-706 resolving an issue with juddi api, delete subscription failing due to
using the wrong service counter metric. admin save subscription also reported a
failure, when it was in fact a success (admin console issue), resolved.
> Add more soap methods to juddi-api service
> ------------------------------------------
>
> Key: JUDDI-706
> URL: https://issues.apache.org/jira/browse/JUDDI-706
> Project: jUDDI
> Issue Type: New Feature
> Components: core
> Reporter: Alex O'Ree
> Assignee: Alex O'Ree
> Fix For: 3.3
>
>
> getAllNodes
> getAllClerks
> deleteNode(String namename)
> deleteClerk(String clerkname)
> adminSaveBusiness - enables you to save a business, while attaching it to
> other username
> adminSavetModel - enables you to save a tModel, while attaching it to other
> username
> Node[] getReplicationNodes() - gets all active replication nodes
> setReplicationNodes(Node[] nodes, boolean removeDeletedNodesData) - sets all
> active replication nodes, option to delete all replicated data from the deltas
> getAllClientSubscriptions()
> alter Node and client code base to include replication API url - added to 3.2
> update admin ui to include the new features
> basically, we want to add everything we would need to configure a multinode
> uddi instance (without a shared database) through the replication api.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
