[
https://issues.apache.org/jira/browse/JUDDI-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Kurt T Stam resolved JUDDI-484.
-------------------------------
Resolution: Fixed
Hi David,
In prior versions we allowed custom tokens. But it experience learned that we
reallly only needed the 'juddi.server.baseur', which is now substituted at
runtime (not install time). This so that different nodes can do the
substitution with their own value if needed. The issue with the tokens at
install time was that if 2 nodes could have different token values and only 1
node would 'win'.
I have updated the user guide accordingly.
Thx,
--Kurt
> The only token modified for seed values is juddi.server.baseurl
> ---------------------------------------------------------------
>
> Key: JUDDI-484
> URL: https://issues.apache.org/jira/browse/JUDDI-484
> Project: jUDDI
> Issue Type: Bug
> Components: core
> Affects Versions: 3.0.4
> Reporter: David Venable
> Assignee: Kurt T Stam
> Priority: Minor
> Fix For: 3.1.0
>
>
> The only token which the jUDDI core substitutes in the seed configuration is
> juddi.server.baseurl. The documentation indicates that other tokens may be
> used. This would also be useful to have.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
