commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject cvs commit: jakarta-commons-sandbox/jelly/xdocs todo.xml
Date Thu, 18 Jul 2002 09:47:50 GMT
jstrachan    2002/07/18 02:47:50

  Modified:    jelly/xdocs todo.xml
  added a bunch more ideas to the todo list (its getting quite large now ;-)
  Revision  Changes    Path
  1.18      +20 -11    jakarta-commons-sandbox/jelly/xdocs/todo.xml
  Index: todo.xml
  RCS file: /home/cvs/jakarta-commons-sandbox/jelly/xdocs/todo.xml,v
  retrieving revision 1.17
  retrieving revision 1.18
  diff -u -r1.17 -r1.18
  --- todo.xml	5 Jul 2002 09:19:39 -0000	1.17
  +++ todo.xml	18 Jul 2002 09:47:50 -0000	1.18
  @@ -16,6 +16,26 @@
       <section name="Core tasks"> 
  +		<li>Implementa a META-INF/services mechanism for mapping Jelly libraries to namespace
  +			in a similar way to how the commons-discovery and JAXP libraries work.
  +			This would allow Jelly libraries to be distributed in a self contained JAR then just
  +			on the classpath and they'd be usable.				
  +			One day it might be interesting to add some funky classloader thing like JJAR/Maven
  +			so that using a new jelly library via a URL would automatically download the jar from
  +			local/remote repository.
  +		</li>
  +		<li>Maybe add a Scope class to make it easier to plugin custom scopes such as 
  +			request, session, applicaiton, initParams, params, transation etc.
  +			In a workflow setting this could also include transient and persistent scopes
  +		</li>
  +		<li>Write a JellyServlet so that Jelly can be used as a page templating system.
  +		</li>
  +		<li>Implement a JellyUnit system so that Jelly cleanly integrates with the JUnit
  +			and Maven's test plugin neatly so that unit tests can be written in jelly script if
  +		</li>
  +		<li>Implement a HTML parser for Jelly, probably using NeckoHTML so that non-XML
can be parsed
  +			and tags with prefixes can be bound to Jelly tags.
  +		</li>
           <li>write a Cocoon JellyGenerator so that Jelly scripts can be used easily
inside Cocoon</li>
   		<li>consider implementing a Jelly Doclet so that Jelly can be used to code generate
   			stuff from javadoc tags in a similar way to XDoclet but making use of the JSTL tags
  @@ -35,12 +55,6 @@
   			Also some of the classes in this package could maybe do with a rename? <br/>
   			ScriptBlock for example - should we just call it a Block or maybe a CompositeScript?
  -		<li>Add parent Context and support for other scopes such as session, <br/>
  -			request, cookie, initParam, param etc.<br/>
  -			Maybe add a Scope class for variable names which can contain a scope name <br/>
  -			and variable name. Then things like  cookie:foo or initParam:bar can be parsed <br/>
  -			at compile time into an object.<br/>
  -		</li>
   		<li>Add an adapter to run JSP tag libraries inside Jelly when Jelly is used in
   			Servlet / JSP environment?
  @@ -72,7 +86,6 @@
           	purely on a SAX stream. Maybe we could wrap <a href="">Joost</a>
           	in a Jelly tag library
  -        <li>Develop a http tag library, probably based on commons-httpclient, that
can be used for scripting web services</li>
           <li>A Betwixt tag library to make it easy to serialize beans to and from
XML from within Jelly scripts.</li>
           <li>Implement a Schematron tag library for validing XML using a path based
approach, rather than schema based.</li>
  @@ -100,10 +113,6 @@
           <li>We could autogenerate XML Schemas or RelaxNG docs for tag libraries to
help validate scripts</li>
           <li>Patch TagLibrary to alias all &lt;mixedCase&gt; tags to &lt;mixed-case&gt;
  -		<li>Provide an alternative non-XML parser such that Jelly scripts do not<br/>
  -			need to be XML. This could allow Velocity-style concise notation <br/>
  -			for common Jelly tags.
  -		</li>

To unsubscribe, e-mail:   <>
For additional commands, e-mail: <>

View raw message