[
https://issues.apache.org/jira/browse/JUDDI-465?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13012696#comment-13012696
]
Kurt T Stam commented on JUDDI-465:
-----------------------------------
The value of the managerName can be set in:
org.apache.juddi.v3.client.manager.name
The value of the nodeName can be set in:org.apache.juddi.v3.client.node.name
I'm also adding a juddi-client-service module which can be used to start/stop
the manager when deployed/undeployed in a sar on JBoss.
> Update the transport.wrapper classes so a managerName and nodeName can be set
> -----------------------------------------------------------------------------
>
> Key: JUDDI-465
> URL: https://issues.apache.org/jira/browse/JUDDI-465
> Project: jUDDI
> Issue Type: Improvement
> Affects Versions: 3.0.4
> Reporter: Kurt T Stam
> Assignee: Kurt T Stam
> Fix For: 3.1.0
>
>
> Right now the scout - jUDDIv3 integration uses the transport.wrapper classes
> in jUDDI. These wrapper classes use a managerName of 'null' and a default
> nodeName of 'default'. We should allow these two parameters to be set using
> system parameters.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
