[
http://issues.apache.org/jira/browse/FOR-800?page=comments#action_12364452 ]
Thorsten Scherler commented on FOR-800:
---------------------------------------
Hmm, I do not understand.
I am looking for all aviable properties. I read something about
default.forrest.properties.xml, ... but which can I request ( I do not know
with which I need to substitute the *)
To pass all this props in the sitemap is not efficient, that is the biggest
problem of input modules in general (you cannot use them directly in xsl).
We can not decide which properties a contract will need and further it is not
easy to extend because you need to touch the sitemap. A contract should be able
to request any given prop from *.properties.xml.
Please see the master.ft:
...
<!-- If you need default variables: -->
<!--<xsl:param name="defaultVariables" select="'test.html'"/>-->
<!-- then extract the variable like: -->
<!--<xsl:variable name="skin-img-dir" select="$defaultVariables/*/[EMAIL
PROTECTED]'skin-img-dir']/@value"/>-->
<!-- more information which variables are aviable can be found at
lm://transform.xml.variable.helper
FIXME: This property xsl is in early stage and aims to be connected
to the new established input module based one.
We need to write a custom generator for this. The generator will
contact the prop-input module to get all aviable key/values and
outputs them to xml (dtd like forrest.properties.xml). -->
> 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
