You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by js...@apache.org on 2002/05/30 21:20:59 UTC
cvs commit: jakarta-commons-sandbox/jelly/xdocs faq.xml
jstrachan 02/05/30 12:20:58
Modified: jelly/xdocs faq.xml
Log:
Added a new FAQ entry on why I named the project Jelly.
Revision Changes Path
1.2 +28 -0 jakarta-commons-sandbox/jelly/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/jakarta-commons-sandbox/jelly/xdocs/faq.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq.xml 28 May 2002 07:14:58 -0000 1.1
+++ faq.xml 30 May 2002 19:20:58 -0000 1.2
@@ -24,6 +24,11 @@
What is Jelly?
</a>
</li>
+ <li>
+ <a href="#why-called-jelly">
+ Why is this called Jelly?
+ </a>
+ </li>
</ol>
<p><strong>Using Jelly</strong></p>
<ol>
@@ -55,6 +60,29 @@
href="overview.html">Overview</a> documents for more detail.
</dd>
</dl>
+
+ <dl>
+ <dt>
+ <a name="why-called-jelly">
+ Why is this called Jelly?
+ </a>
+ </dt>
+ <dd>
+ The name started out as 'Jele' as in Java ELEments but then I thought Jelly was a nicer spelling :-).
+ The basic idea behind Jelly that Java code is bound on to XML elements.
+ </dd>
+ <dd>
+ Also Jelly (in British or Jello in American) can be molded to fit any shape required which kinda fits
+ with Jelly's main aim to be a flexible Java and XML based scripting engine that can do anything.
+ </dd>
+ <dd>
+ There are many different specific frameworks that take an XML document, bind it to some kind of bean or object
+ and then evaluate it in some kind of script or process, so Jelly was an attempt at a generic engine
+ using ideas from JSP, JSTL, Velocity, Cocoon and Ant.
+ </dd>
+ </dl>
+
+
</section>
<section name="Using Jelly">
<dl>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>