Details

    • Type: Task Task
    • Status: Open
    • Priority: Critical Critical
    • Resolution: Unresolved
    • Affects Version/s: None
    • Fix Version/s: 0.10-dev
    • Component/s: Core operations
    • Labels:
      None

      Description

      We need a new config system for Forrest for various reasons: the initial config system was known to be limited; to enable the specification of multiple Forrest sites within a single instance of Forrest; to accommodate the changes brought about by forrest:views, themes, and plugins.

        Issue Links

          Activity

          Hide
          Ross Gardler added a comment -
          Show
          Ross Gardler added a comment - Some discussion: http://marc.theaimsgroup.com/?t=112299875300003&r=1&w=2
          Hide
          Ross Gardler added a comment -
          Show
          Ross Gardler added a comment - An RT on how to integrate multiple sites: http://marc.theaimsgroup.com/?l=forrest-dev&m=112387459426160&w=2
          Hide
          David Crossley added a comment -
          This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- FOR-618 "Create issues for items discussed at Apachecon"
           
          Some devs had an initial discussion. The notes are in SVN at
          http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005/
          Show
          David Crossley added a comment - This issue is the result of an ApacheCon discussion, more, including links to the original ApacheCon Summaries at :- FOR-618 "Create issues for items discussed at Apachecon"   Some devs had an initial discussion. The notes are in SVN at http://svn.apache.org/repos/asf/forrest/events/apachecon-eu-2005/
          Hide
          David Crossley added a comment -
          NOTE: For any users thinking ("oh no, the next forrest will be hard to upgrade because of fundamental changes in the way it is configured", don't worry. We will (most likely) provide tools to facilitate this upgrade, we will need them ourselves anyway).
          Show
          David Crossley added a comment - NOTE: For any users thinking ("oh no, the next forrest will be hard to upgrade because of fundamental changes in the way it is configured", don't worry. We will (most likely) provide tools to facilitate this upgrade, we will need them ourselves anyway).
          Hide
          Ross Gardler added a comment -
          Show
          Ross Gardler added a comment - Using locationmap as a config system: http://marc.theaimsgroup.com/?l=forrest-dev&m=112827771411900&w=2
          Hide
          Ross Gardler added a comment -
          A new set of properties can now be defined in a "forrest.properties.xml" file in the root of the project. These properties are not defined in forrest.xconf, thus any property can be defined in this file. This enables plugins to define their own property values. Although at the time of writing functionality is minimal.

          The format of the file is:

          <?xml version="1.0" encoding="UTF-8"?>
          <properties>
                 <property name="daisy.navigation.docID" value="1208"/>
          </properties>

          Properties are retrieved in the sitemap and the locationmap (untested) using {project:PROPERTY.NAME}.

          Currently there is no mechanism for loading defaults for plugin properties. This needs to be added.

          In addition to plugins being able to define properties that can be overridden by the project properties file this addition enables us to remove the need to define properties in forrest.xconf.
          Show
          Ross Gardler added a comment - A new set of properties can now be defined in a "forrest.properties.xml" file in the root of the project. These properties are not defined in forrest.xconf, thus any property can be defined in this file. This enables plugins to define their own property values. Although at the time of writing functionality is minimal. The format of the file is: <?xml version="1.0" encoding="UTF-8"?> <properties>        <property name="daisy.navigation.docID" value="1208"/> </properties> Properties are retrieved in the sitemap and the locationmap (untested) using {project:PROPERTY.NAME}. Currently there is no mechanism for loading defaults for plugin properties. This needs to be added. In addition to plugins being able to define properties that can be overridden by the project properties file this addition enables us to remove the need to define properties in forrest.xconf.
          Hide
          Ross Gardler added a comment -
          We have a prototype solution in place for 0.8-dev

          This solution solves the immediate problems for configuring plugins.

          Reducing priority and moving to 0.9 when we will complete this functionaliy.
          Show
          Ross Gardler added a comment - We have a prototype solution in place for 0.8-dev This solution solves the immediate problems for configuring plugins. Reducing priority and moving to 0.9 when we will complete this functionaliy.
          Hide
          Ross Gardler added a comment -
          The process for doing this will change when the new property system is adopted (being prototyped in 0.8-dev)
          Show
          Ross Gardler added a comment - The process for doing this will change when the new property system is adopted (being prototyped in 0.8-dev)
          Hide
          Thorsten Scherler added a comment -
          The dispatcher needs an aggregation of forrest.properties.xml.
          Show
          Thorsten Scherler added a comment - The dispatcher needs an aggregation of forrest.properties.xml.
          Hide
          David Crossley added a comment -
          More discussion is at:
           RT: Storage of Properties
           http://marc.info/?t=120370236700002
          Show
          David Crossley added a comment - More discussion is at:  RT: Storage of Properties   http://marc.info/?t=120370236700002

            People

            • Assignee:
              Unassigned
              Reporter:
              Ross Gardler
            • Votes:
              0 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:

                Development