Author: thorsten
Date: Mon May 14 01:26:43 2007
New Revision: 537748
URL: http://svn.apache.org/viewvc?view=rev&rev=537748
Log:
Updating FIXME note in the master contract and adding more infos to the
properties part of the dispatcher documentation.
Modified:
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/int/index.xml
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/common/html/master.ft
Modified:
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/int/index.xml
URL:
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/int/index.xml?view=diff&rev=537748&r1=537747&r2=537748
==============================================================================
---
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/int/index.xml
(original)
+++
forrest/trunk/whiteboard/plugins/org.apache.forrest.plugin.internal.dispatcher/src/documentation/content/xdocs/int/index.xml
Mon May 14 01:26:43 2007
@@ -47,6 +47,22 @@
<property name="dispatcher.themer" value="org.apache.forrest.themes.core"/>
<property name="dispatcher.home"
value="org.apache.forrest.plugin.internal.dispatcher"/>]]>
</source>
+ <section>
+ <title>Using properties in contracts</title>
+ <p> In the contract body you can access all forrest properties by</p>
+ <source>
+ <![CDATA[<xsl:param name="defaultVariables" select="'test.html'"/>]]>
+ </source>
+ <p>then extract the variable like:</p>
+ <source>
+ <![CDATA[<xsl:variable name="skin-img-dir"
select="$defaultVariables/*/[EMAIL PROTECTED]'THE_PROPERTY']/@value"/>]]>
+ </source>
+ <p>more information which variables are available can be found at
+ http://localhost:8888/**.props which connects to the
+ org.apache.forrest.plugin.output.inputModule plugin. A custom
generator
+ contacts the forrest properties input module to get all aviable
key/values and
+ outputs them to xml (dtd like forrest.properties.xml). </p>
+ </section>
</section>
<section id="lm">
<title>locationmap.xml</title>
Modified:
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/common/html/master.ft
URL:
http://svn.apache.org/viewvc/forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/common/html/master.ft?view=diff&rev=537748&r1=537747&r2=537748
==============================================================================
---
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/common/html/master.ft
(original)
+++
forrest/trunk/whiteboard/plugins/org.apache.forrest.themes.core/themes/common/html/master.ft
Mon May 14 01:26:43 2007
@@ -39,11 +39,10 @@
<!--<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 available 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). -->
+<!-- more information which variables are available can be found at
http://localhost:8888/**.props
+ which connects to the org.apache.forrest.plugin.output.inputModule plugin.
+ A custom generator contacts the forrest properties input module to get
all aviable key/values and
+ outputs them to xml (dtd like forrest.properties.xml). -->
<!-- Since contracts are standalone every implementation has to be invoked by
some input.-->
<!-- That means for xsl contracts that they are working for any xml input.
We need to match the root element to invoke the contract
processing!!!
