[
https://issues.apache.org/jira/browse/JUDDI-588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13630899#comment-13630899
]
Kurt T Stam commented on JUDDI-588:
-----------------------------------
This is intended behavior; the juddi db can be shared by multiple jUDDI nodes,
so on the way out it replaces the ${juddi.server.baseurl} with the address
specified in that node's juddiv3.properties file. This is to support a
distributed jUDDI deployment. However we need to make sure we covered "all the
ways out" with the token replacement, and you are saying that "it doesn't work
for Discovery URLs on business elements". So we may have a bug there. I will
investigate. Should be an easy fix.
> Default Juddi business has services with endpoints starting with
> ${juddi.server.baseurl}/juddiv3
> ------------------------------------------------------------------------------------------------
>
> Key: JUDDI-588
> URL: https://issues.apache.org/jira/browse/JUDDI-588
> Project: jUDDI
> Issue Type: Improvement
> Reporter: Alex O'Ree
> Assignee: Kurt T Stam
> Priority: Minor
>
> Default Juddi business has services with endpoints starting with
> ${juddi.server.baseurl}/juddiv3. This isn't useful and should be replaced
> with either localhost or the hostname of the local machine. Something like
> String localhostname = java.net.InetAddress.getLocalHost().getHostName();
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
