Uploaded image for project: 'Jackrabbit Content Repository'
  1. Jackrabbit Content Repository
  2. JCR-1694

System properties does not get replaced in a Cluster configuration

    Details

    • Type: Bug
    • Status: Closed
    • Priority: Major
    • Resolution: Fixed
    • Affects Version/s: core 1.4.5
    • Fix Version/s: 1.5
    • Component/s: config
    • Labels:
      None

      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?

        Attachments

        1. JCR-1694-testcase.diff
          10 kB
          fabrizio giustina
        2. JCR-1694-fix.diff
          11 kB
          fabrizio giustina

          Issue Links

            Activity

              People

              • Assignee:
                dpfister Dominique Pfister
                Reporter:
                fgiust fabrizio giustina
              • Votes:
                0 Vote for this issue
                Watchers:
                2 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: