commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jstrac...@apache.org
Subject cvs commit: jakarta-commons-sandbox/jelly/xdocs faq.xml navigation.xml
Date Tue, 28 May 2002 07:14:58 GMT
jstrachan    02/05/28 00:14:58

  Modified:    jelly/xdocs navigation.xml
  Added:       jelly/xdocs faq.xml
  Log:
  Finally added a FAQ with a couple of common entries in it.
  
  Revision  Changes    Path
  1.3       +1 -0      jakarta-commons-sandbox/jelly/xdocs/navigation.xml
  
  Index: navigation.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/jelly/xdocs/navigation.xml,v
  retrieving revision 1.2
  retrieving revision 1.3
  diff -u -r1.2 -r1.3
  --- navigation.xml	21 May 2002 16:53:26 -0000	1.2
  +++ navigation.xml	28 May 2002 07:14:58 -0000	1.3
  @@ -7,6 +7,7 @@
     <body>
       <menu name="Jelly">
         <item name="Overview"                href="/index.html"/>
  +      <item name="FAQ"                     href="/faq.html"/>
         <item name="Detail"                  href="/overview.html"/>
       </menu>
     </body>
  
  
  
  1.1                  jakarta-commons-sandbox/jelly/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  <?xml version="1.0"?>
  
  <document>
  
    <properties>
      <title>Maven FAQ</title>
      <author email="jstrachan@apache.org">James Strachan</author>
    </properties>
  
    <body>
  
    <section name="Frequently Asked Questions">
      <p>
        This document attempts to answer some of the more frequently asked
        questions regarding various aspects of Jelly.  These questions are
        typically asked over and over again on the mailing lists, as a
        courtesy to the developers, we ask that you read this document
        before posting to the mailing lists.  
      </p>
      <p><strong>General</strong></p>
      <ol>
        <li>
          <a href="#what-is-jelly">
            What is Jelly?
          </a>
        </li>
      </ol>
      <p><strong>Using Jelly</strong></p>
      <ol>
        <li>
          <a href="#adding-taglibs">
            How do I add my own tag libraries to Jelly?
          </a>
        </li>
      </ol>
      <p><strong>Building Jelly</strong></p>
      <ol>
        <li>
          <a href="#how-to-build">
            How do I build Jelly?
          </a>
        </li>
      </ol>
  
      <section name="General">
        <dl>
          <dt>
            <a name="what-is-jelly">
              What is Jelly?
            </a>
          </dt>
          <dd>
            Jelly is an open and customizable XML processing engine.
            Please see the <a href="index.html">Home page</a> and <a
            href="overview.html">Overview</a> documents for more detail.
          </dd>
        </dl>
      </section>
      <section name="Using Jelly">
        <dl>
          <dt>
            <a name="adding-taglibs">
              How do I add my own tag libraries to Jelly?
            </a>
          </dt>
          <dd>
            Firstly you need to create one or more tags, by deriving from TagSupport.
            Then create a TagLibrary class for your tags; typically all this does
            is register all the tags in your tag library and give them names.          
            Then you can use your new tag library by specifying the classname in
            a namespace URI. For example
          </dd>
          <dd>
  <code>
  <pre>
  &lt;j:jelly xmlns:j="jelly:core" xmlns:foo="jelly:com.acme.something.MyTagLibrary"&gt;
  
    &lt;foo:bar x="12&gt;
  	something goes here
    &lt;/foo:bar&gt;
  
  &lt;/j:jelly&gt;
  </pre>
  </code>
          </dd>
          <dd>                
            Going forward we hope to provide an alias mechanism using the jar-extension
            mechanism used by JAXP so that a file could be placed on the classpath 
  		  called <code>META-INF/services/org.apache.commons.jelly.foo</code> which
  		  would contain the class name of the tag library (com.acme.something.MyTagLibrary)
  		  then you could use it as follows, which would avoid using the class name in your scripts.
          </dd>
          <dd>                
  <code>
  <pre>
  &lt;j:jelly xmlns:j="jelly:core" xmlns:foo="jelly:foo"&gt;
  
    &lt;foo:bar x="12&gt;
  	something goes here
    &lt;/foo:bar&gt;
  
  &lt;/j:jelly&gt;
  </pre>
  </code>
  		</dd>
        </dl>
      </section>
      <section name="Building Jelly">
        <dl>
          <dt>
            <a name="how-to-build">
              How do I build Jelly?
            </a>
          </dt>
          <dd>
            Jelly uses Maven for its build system. So you should be able to build Jelly just
like
            any other Maven enabled project. Please see the 
            <a href="http://jakarta.apache.org/turbine/maven/start/index.html">Maven</a>

            documentation for details.
          </dd>
        </dl>
      </section>
    </section>
  </body>
  </document>
  
  
  

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message