[JCR-1694] System properties does not get replaced in a Cluster configuration

• Type: Bug
• Status: Closed
• Priority: Major
• Resolution: Fixed
• Affects Version/s: core 1.4.5
• Fix Version/s: 1.5
• Component/s: config
• Assignee: Dominique Pfister
• Reporter: Fabrizio Giustina
• Created: 27/Jul/08 08:05
• Updated: 08/Dec/08 11:09
• Resolved: 16/Sep/08 08:35

Description

Since JCR-1304 has been added to jackrabbit 1.4 I guess this should be reported as a bug...

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?

Issue Links

• is part of: JCR-1304 Support system properties in ${...} vars in XML config files