Things To Do for Apache Cocoon 2
http://xml.apache.org/http://www.apache.org/http://www.w3.org/

Index
License
Cocoon
Installing
Overview
cTwIG
Users
Developers
Links
XML Links
Infos
Who we are
Contributing
3rd Party
Patch Queue
Status
FAQ File
Changes
Todo
Hosting
Live Sites
Cocoon Hosting
Project
Bug Database
Code Repository
Dev Snapshots
Mail Lists
Mail Archives

high
  • [code] Make the use of Batik optional to avoid the X-server problem.
  • [code] Structure the documentation. Currently it is a flat structure. There are several proposals for a better structuring.
  • [code] Update the documentation to reflect recent changes and divide it into user and developer documentation.
  • [code] Complete (means put everything we know of into even if it has to be commented) the cocoon.xconf file and put descriptions into it
  • [code] Complete (means put everything we know of into even if it has to be commented) the web.xml file and put descriptions into it (similar to the httpd.conf file of the web server or the server.xml of Catalina)

medium
  • [code] Remove deprecated methods from org.apache.cocoon.xml.util and make it clean for SAX2 final.
  • [code] Finish writing the command line interface and design the link rewriting behavior that cannot work with views.
  • [code] Complete/write documentation in general.
  • [code] Check if the map:redirect-to should handle all urls including the special cocoon: protocol. This would require making the redirect for these urls on the server.
  • [code] Check how to handle the mixing of output streams when an error inside a pipeline occurs. When the pipeline has something written to the output stream and then an error occurs the result is the first written part with the appended exception. One solution could be a configurable intermediate output stream.
  • [code] Update and improve the profiling tool from the HEAD cvs and incorporate it into the 2.0 branch.

Copyright © 1999-2001 The Apache Software Foundation. All Rights Reserved.