cziegeler 01/06/22 01:34:10
Modified: . Tag: cocoon_20_branch build.xml
xdocs Tag: cocoon_20_branch caching.xml
Added: bin Tag: cocoon_20_branch st.class
bin/src Tag: cocoon_20_branch st.java
Log:
Added sitemap command line tool which can add component declarations during
the build process
Revision Changes Path
No revision
No revision
1.8.2.9 +21 -2 xml-cocoon2/build.xml
Index: build.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/build.xml,v
retrieving revision 1.8.2.8
retrieving revision 1.8.2.9
diff -u -r1.8.2.8 -r1.8.2.9
--- build.xml 2001/06/21 12:59:14 1.8.2.8
+++ build.xml 2001/06/22 08:34:06 1.8.2.9
@@ -348,9 +348,9 @@
</target>
<!-- ===================================================================
-->
- <!-- Prapares the webapp directories
-->
+ <!-- Copies the webapp directories
-->
<!-- ===================================================================
-->
- <target name="prepare-webapp" depends="prepare">
+ <target name="copy-webapp" depends="prepare">
<mkdir dir="${build.war}"/>
<copy todir="${build.war}" filtering="on">
@@ -374,7 +374,26 @@
<fileset dir="${webapp.dir}/i18n">
</fileset>
</copy>
+ </target>
+
+ <!-- ===================================================================
-->
+ <!-- Prapares the webapp sitemap if php is available
-->
+ <!-- ===================================================================
-->
+ <target name="prepare-webapp-php" depends="copy-webapp" if="php.present">
+ <java classname="st">
+ <arg line="-i ${build.war}/sitemap.xmap -o
${build.war}/sitemap.xmap2 -a generators php
org.apache.cocoon.generation.PhpGenerator"/>
+ <classpath>
+ <pathelement location="${bin.dir}"/>
+ </classpath>
+ </java>
+ </target>
+
+ <!-- ===================================================================
-->
+ <!-- Prepares the webapp directories
-->
+ <!-- ===================================================================
-->
+ <target name="prepare-webapp" depends="copy-webapp, prepare-webapp-php">
+ <!-- Simply do nothing, just invoke all dependencies -->
</target>
<!-- ===================================================================
-->
No revision
No revision
1.1.2.1 +0 -0 xml-cocoon2/bin/st.class
<<Binary file>>
No revision
No revision
1.1.2.1 +0 -0 xml-cocoon2/bin/src/st.java
Index: st.java
===================================================================
RCS file: /home/cvs/xml-cocoon2/bin/src/st.java,v
retrieving revision 1.1
retrieving revision 1.1.2.1
diff -u -r1.1 -r1.1.2.1
--- st.java 2001/06/22 08:32:31 1.1
+++ st.java 2001/06/22 08:34:08 1.1.2.1
@@ -28,7 +28,7 @@
* Pretty printing
*
* @author <a href="mailto:[EMAIL PROTECTED]">Carsten Ziegeler</a>
- * @version CVS $Revision: 1.1 $ $Date: 2001/06/22 08:32:31 $
+ * @version CVS $Revision: 1.1.2.1 $ $Date: 2001/06/22 08:34:08 $
*/
public class st {
No revision
No revision
1.1.2.3 +19 -0 xml-cocoon2/xdocs/caching.xml
Index: caching.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/xdocs/caching.xml,v
retrieving revision 1.1.2.2
retrieving revision 1.1.2.3
diff -u -r1.1.2.2 -r1.1.2.3
--- caching.xml 2001/06/20 14:46:31 1.1.2.2
+++ caching.xml 2001/06/22 08:34:09 1.1.2.3
@@ -75,6 +75,25 @@
<p>Now after the key is build for this particular
request, it is looked up
in the cache if it exists. If not, the new request is
generated and cached
for further requests.</p>
+ <p>If a cached response is found for the key, the caching
algorithm checks
+ if this response is still valid. For this check each
cacheable component
+ returns a validity object when the method
<code>generateValidity</code>
+ is invoked. (If a cacheable component returns
<code>null</code> it
+ is temporarily not cacheable, like returning
<code>0</code> for the key.)</p>
+ <p>A <code>CacheValidity</code> object contains all
information the component
+ needs to verify if the cached content is still valid.
For example the
+ file generator stores the last modification date of the
xml document parsed
+ in the validity object.</p>
+ <p>When a response is cached all validity objects are
stored together with
+ the cached response in the cache. Actually the
<code>CachedEventObject</code>
+ is stored which encapsulates all this information.</p>
+ <p>When a new response is generated and the key is
generated, the caching
+ algorithm also collects all uptodate cache validity
objects. So if the
+ cached response is found in the cache these validity
objects are compared.
+ If they are valid (or equal) the cached response is
used and feed into
+ the pipeline. If they are not valid any more the cached
response is removed
+ from the cache, the new response is generated and then
stored together with
+ the new validity objects in the cache.</p>
<p>To be continued...</p>
<s3 title="Example">
<p>Guess what! Yes, forthcoming.</p>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
