Forrest
  1. Forrest
  2. FOR-1071

configure main sitemap components, e.g. output html serializer

    Details

    • Type: Bug Bug
    • Status: Closed
    • Priority: Major Major
    • Resolution: Fixed
    • Affects Version/s: 0.8, 0.9
    • Fix Version/s: 0.9
    • Component/s: Core operations
    • Labels:
      None
    • Other Info:
      Patch available

      Description

      There is a need modify certain Cocoon sitemap components, however these are hard-coded in the forrest core at main/webapp/sitemap.xmap file. For example, the output html serializer is hard-coded to be HTML 4.01 Transitional doctype declaration.

        Activity

        Hide
        David Crossley added a comment -
        Here are some links to old discussions, perhaps there are more:

        Re: [[use of a xconf variable]
        http://thread.gmane.org/gmane.text.xml.forrest.devel/21322/focus=21693

        LM properties lookup for JTidy
        http://markmail.org/message/twrwhxggbzgriva4

        Cyriaque then took the issue to COCOON-1928. The discussion is great and explains why most configuration methods are too late in the process - the Cocoon components has already been established.
        Show
        David Crossley added a comment - Here are some links to old discussions, perhaps there are more: Re: [[use of a xconf variable] http://thread.gmane.org/gmane.text.xml.forrest.devel/21322/focus=21693 LM properties lookup for JTidy http://markmail.org/message/twrwhxggbzgriva4 Cyriaque then took the issue to COCOON-1928 . The discussion is great and explains why most configuration methods are too late in the process - the Cocoon components has already been established.
        Hide
        David Crossley added a comment -
        One decent solution is to use "xml entities" declared in the main sitemap. Since v0.8 we already enable sets of symbols using this technique.
        http://forrest.apache.org/docs/faq.html#xml-entities
        http://forrest.zones.apache.org/ft/build/forrest-seed/samples-b/xml-entities.html

        I have a solution working and will commit it soon. Need to test in Dispatcher and make some docs.

        Show
        David Crossley added a comment - One decent solution is to use "xml entities" declared in the main sitemap. Since v0.8 we already enable sets of symbols using this technique. http://forrest.apache.org/docs/faq.html#xml-entities http://forrest.zones.apache.org/ft/build/forrest-seed/samples-b/xml-entities.html I have a solution working and will commit it soon. Need to test in Dispatcher and make some docs.
        Hide
        David Crossley added a comment -
        Added this ability in r632740. See faq.html#sitemap-entities

        The "Symbols Project" file is declared in the core xml catalog. Then each project can over-ride this to provide their own "Symbols Project" file and so be able to declare their own entities to over-ride those from "Symbols Core". Thus these substitutions can occur early in the Cocoon start-up process.
        Show
        David Crossley added a comment - Added this ability in r632740. See faq.html#sitemap-entities The "Symbols Project" file is declared in the core xml catalog. Then each project can over-ride this to provide their own "Symbols Project" file and so be able to declare their own entities to over-ride those from "Symbols Core". Thus these substitutions can occur early in the Cocoon start-up process.
        Hide
        David Crossley added a comment -
        Re-opened this issue and reverted at r633330, as there was a resulting issue in a 'forrest seed-basic' site with poor declaration in the xml catalog. See FOR-1075.
        Show
        David Crossley added a comment - Re-opened this issue and reverted at r633330, as there was a resulting issue in a 'forrest seed-basic' site with poor declaration in the xml catalog. See FOR-1075 .
        Hide
        David Crossley added a comment -
        Re-implemented this feature in r633365.

        Users prior to version 0.8, and developers after today r633365, should have no problems, as the default entity resolver handles it.

        Users of 0.8, and developers with older 0.9-dev, who based their sites on 'forrest seed-basic' rather than 'forrest seed-sample' will be affected by FOR-1075. To workaround that, there is an empty file at main/webapp/symbols-project-v10.ent file.

        In any case all users of 0.9+ should ensure that they have a "project symbols" file and take advantage of this sitemap configuration ability. See http://forrest.apache.org/docs/dev/faq.html#sitemap-entities
        Show
        David Crossley added a comment - Re-implemented this feature in r633365. Users prior to version 0.8, and developers after today r633365, should have no problems, as the default entity resolver handles it. Users of 0.8, and developers with older 0.9-dev, who based their sites on 'forrest seed-basic' rather than 'forrest seed-sample' will be affected by FOR-1075 . To workaround that, there is an empty file at main/webapp/symbols-project-v10.ent file. In any case all users of 0.9+ should ensure that they have a "project symbols" file and take advantage of this sitemap configuration ability. See http://forrest.apache.org/docs/dev/faq.html#sitemap-entities

          People

          • Assignee:
            Unassigned
            Reporter:
            David Crossley
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved:

              Development