You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@forrest.apache.org by "Thorsten Scherler (JIRA)" <ji...@apache.org> on 2006/01/28 20:47:35 UTC
[jira] Created: (FOR-800) make forrest.properties.xml (as
aggregation of all properties) aviable via cocoon://
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
[jira] Commented: (FOR-800) make forrest.properties.xml (as
aggregation of all properties) aviable via cocoon://
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-800?page=comments#action_12365879 ]
Ross Gardler commented on FOR-800:
----------------------------------
Cocoons XMLFileInputModule may be the answer (http://cocoon.apache.org/2.1/apidocs/org/apache/cocoon/components/modules/input/XMLFileModule.html)
> 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
[jira] Commented: (FOR-800) make forrest.properties.xml (as
aggregation of all properties) aviable via cocoon://
Posted by "Ross Gardler (JIRA)" <ji...@apache.org>.
[ 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
[jira] Closed: (FOR-800) make forrest.properties.xml (as
aggregation of all properties) aviable via cocoon://
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/FOR-800?page=all ]
Thorsten Scherler closed FOR-800.
---------------------------------
Resolution: Fixed
The last remaining issue was implementing the Iterator getAttributeNames in the
ForrestConfModule. To see all aviable properties add
org.apache.forrest.plugin.output.inputModule and request
cocoon://module.project.properties.
> 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
> Issue 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
[jira] Commented: (FOR-800) make forrest.properties.xml (as
aggregation of all properties) aviable via cocoon://
Posted by "Thorsten Scherler (JIRA)" <ji...@apache.org>.
[ 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/*/*[@name='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