jackrabbit-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "fabrizio giustina (JIRA)" <j...@apache.org>
Subject [jira] Commented: (JCR-1694) System properties does not get replaced in a Cluster configuration
Date Sun, 27 Jul 2008 12:32:31 GMT

    [ https://issues.apache.org/jira/browse/JCR-1694?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12617280#action_12617280

fabrizio giustina commented on JCR-1694:

(if the patch looks good it would be great to have it merged to the 1.4 branch for the upcoming
1.4.6 release, thanks)

> System properties does not get replaced in a Cluster configuration
> ------------------------------------------------------------------
>                 Key: JCR-1694
>                 URL: https://issues.apache.org/jira/browse/JCR-1694
>             Project: Jackrabbit
>          Issue Type: Bug
>          Components: config
>    Affects Versions: core 1.4.5
>            Reporter: fabrizio giustina
>         Attachments: JCR-1694-fix.diff, JCR-1694-testcase.diff
> Since JCR-1304 has been added to jackrabbit 1.4 I guess this should be reported as a
> Still not debugged deeply, but if I try to configure a Cluster using:
> <Cluster id="${server}" syncDelay="10">
> after setting a "server" system property I expect to have the cluster initialized properly
using the value of such property... I just realized that my cluster node gets initialized
with the final value of "${server}" instead :(
> Cluster config is a very good place where to use system properties, since all the configuration
is usually identical between cluster nodes while the "id" property must be different...
> Is there anything I missed/did wrong in my configuration?

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message