Things To Do
http://xml.apache.org/http://www.apache.org/http://www.w3.org/

Index
News
License
Download

Documentation
Introduction
Installing
Overview
User Guide
Dev Guide
Tutorials
FAQs
How-Tos
Performance
Snippets
ToC

Status
Changes
Todo
Planning notes
Patch queue

Community
Cocoon Bylaws
Hall of Fame
Contributing
Mail Lists
Mail Archives

Project
Bug Database
Code Repository
Dev Snapshots

Links
Cocoon Links
Live Sites
Cocoon Hosting

Other Releases
Cocoon 1.x
Cocoon 2.1

high
  • [code] For 2.1: Rewrite the FilesystemStore. The current implementations relies on a correct implementation of the toString() method of the used keys. A correct version should rely on hashCode() and equals(). (This is actually an Avalon action as the code is in Excalibur)
  • [code] For 2.1: Implement the smart-caching for the processing pipeline and iron out bugs.
  • [docs] For 2.1: Attend to any high+ issues in the Documentation To Do List
  • [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 all allowed constructs and combinations) the lint/sitemap.xmap file. Enhance the RELAX NG grammar for sitemap.
  • [code] For 2.1: Views must start not from the first encountered label, but from the last one (see http://marc.theaimsgroup.com/?l=xml-cocoon-dev&m=101784499622172&w=2)
  • [code] For 2.1: Make comprehensive samples with the handle-errors sitemap and real world use cases. Add also specific Selector and a FaqBuilder to be used by the as a NotifyingBuilder.
  • [code] For 2.1: Make all the samples in WIP (Work In Progress) work again, and finish refactoring.
medium
  • [code] Remove all useless blank strings in XSP-generated code that hinder performances. This should be configurable (through an attribute?) to be able to keep them when needed.
  • [code] For 2.1: Make a guide on how to upgrade Cocoon,and see how this can be eased.
  • [code] For 2.1: 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] For 2.1: Redesign FragmentExtractorGenerator/Transformer so that it works on a clustered server : store fragments in the session rather than in a local store.
    Additionnaly, store the fragments using the XMLCompiler instead of building a DOM.
Copyright © 1999-2002 The Apache Software Foundation. All Rights Reserved.