[
http://issues.apache.org/jira/browse/FOR-800?page=comments#action_12364447 ]
Ross Gardler commented on FOR-800:
----------------------------------
The properties file is XML, just add a mather to the core sitemap, e.g.:
<map:match pattern="*.properties.xml">
<map:read src="{lm:properties.{1}}"/>
</map:match>
However, I've not done this, partly because I don't have the time to test right
now and partly because I don't see the need. All properties are available to
the sitemap and from there they can be passed to any resource in the pipeline.
Can you give a use case where this is necessary (I know we have discussed this
on the ML but there has been no use case for it yet).
> make forrest.properties.xml (as aggregation of all properties) aviable via
> cocoon://
> ------------------------------------------------------------------------------------
>
> Key: FOR-800
> URL: http://issues.apache.org/jira/browse/FOR-800
> Project: Forrest
> Type: Sub-task
> Components: Core operations
> Reporter: Thorsten Scherler
> Priority: Blocker
>
> That the new properties is usable to a wider range of use cases we need to be
> able to request all of them via on match.
> Either project specific like:
> cocoon://forrest.properties.xml
> or path specific like:
> cocoon://**.properties.xml
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
