You are viewing a plain text version of this content. The canonical link for it is here.
Posted to taglibs-dev@jakarta.apache.org by sh...@apache.org on 2002/04/03 06:23:20 UTC

cvs commit: jakarta-taglibs/cache/xml cache.xml

shawn       02/04/02 20:23:20

  Modified:    cache    build.xml
               cache/xml cache.xml
  Log:
  Minor updates.
  
  Revision  Changes    Path
  1.2       +9 -30     jakarta-taglibs/cache/build.xml
  
  Index: build.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-taglibs/cache/build.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- build.xml	3 Apr 2002 03:26:29 -0000	1.1
  +++ build.xml	3 Apr 2002 04:23:20 -0000	1.2
  @@ -6,44 +6,23 @@
   
   <project name="cache" default="main">
   
  -  <property name="taglib.name" value="cache" />
  -
  -  <!-- By default, common.xml adds servlet.jar to the classpath
  -       ant uses when building your taglib.  If you need to use
  -       additional jar files or this is a JSP1.2 taglib you will
  -       have to override the ant definition of the classpath by
  -       uncommenting the below declarations and adding any required
  -       jar files to the ant classpath. -->
  -
  -  <!-- Load in your local build properties which define jar
  -       file locations.
  -  <property file="../build.properties"/> -->
  -  <!-- Define additional jar files to be used by ant when
  -       building your taglib.  The classpath value is a ":"
  -       separated list of jar file property names from your
  -       local build.properties file. Use servlet23.jar instead
  -       of servlet.jar if this is a JSP1.2 taglib.
  -  <property name="classpath" value="${servlet.jar}:${standard.jar}"/> -->
  -  <!-- Define the property jsp12.present if this is a JSP 1.2 taglib
  -  <property name="jsp12.present" value="true"/> -->
  -
  -  <!-- common.xml defines a number of targets in its build process
  -       which you can override in your local build.xml file.  In this
  -       case we want to override the ant target "checkRequirements.pre"
  -       so that we can verify that the required jar files are present. -->
  +  <!-- <property name="taglib.name" value="cache"/> -->
  +  <property file="../build.properties"/>
  +  <property name="classpath" value="${servlet.jar}:${standard.jar}"/>
     <property name="checkRequirements.pre" value="checkRequirements.pre"/>
  -
  -
  -  <!-- Here is the ant target that overrides "checkRequirements.pre" -->
  +  <property name="examples.pre" value="examples.pre"/>
     <target name="checkRequirements.pre">
       <antcall target="checkRequiredFile">
          <param name="file" value="${standard.jar}"/>
  -       <param name="fail.message" value="The JSTL JAR file, standard.jar, is not available.  Please define the property standard.jar in your build.properties file and ensure that the file exists"/>
  +       <param name="fail.message" value="The JSTL JAR file, standard.jar, is not available.  Please define the property standard.jar in your build.properties file and ensure that the file exists."/>
       </antcall>
     </target>
   
  +  <target name="examples.pre">
  +    <copy todir="${build.examples}/WEB-INF/lib" file="${standard.jar}"/>
  +  </target>
  +
     <!-- Include the common.xml ant build declarations -->
     &common;
   
   </project>
  -
  
  
  
  1.2       +21 -0     jakarta-taglibs/cache/xml/cache.xml
  
  Index: cache.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-taglibs/cache/xml/cache.xml,v
  retrieving revision 1.1
  retrieving revision 1.2
  diff -u -r1.1 -r1.2
  --- cache.xml	3 Apr 2002 03:26:35 -0000	1.1
  +++ cache.xml	3 Apr 2002 04:23:20 -0000	1.2
  @@ -34,6 +34,22 @@
          the default cache size is 64k.  These are both configurable
          by back-end Java developers using the CacheUtil class included
          with this library.</p>
  +
  +       <p>Caching is a discipline whose details are probably best left
  +       unexposed to page authors in large environments.  Therefore,
  +       the Cache Taglib's interface has been designed to be as simple
  +       as possible.  The tag attributes let page authors "factor out"
  +       the dynamic nature of a page fragment into a simple <i>key</i>;
  +       fragments with the same key have interchangeable content.
  +       For example, in a fragment whose content depends only on who
  +       the current user is, <tt>${user}</tt> might be a good key.  Keys
  +       can be formed from more complex expressions too.  For instance,
  +       if a fragment's content depends on the current user <i>and</i>
  +       the user's chosen verbosity level, you might use an attribute
  +       like <tt>key="${user}.${verbosity}"</tt></p>
  +
  +       <p>Note that the Cache Taglib currently uses the expression
  +       language (EL) from Beta1 of the JSTL reference implementation.</p>
     </description> 
   
    <!--
  @@ -260,6 +276,11 @@
   </revision>
       -->
   
  +<revision release="Development" date="04/02/2002">
  +  <description>
  +    Cache Taglib imported into CVS.
  +  </description>
  +</revision>
   <revision release="Development" date="03/30/2002">
     <description>
       Work on the Cache Taglib initiated.
  
  
  

--
To unsubscribe, e-mail:   <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>