cziegeler 01/07/13 02:45:05
Modified: . Tag: cocoon_20_branch todo.xml
Log:
Updated todo
Revision Changes Path
No revision
No revision
1.1.1.1.2.6 +19 -14 xml-cocoon2/todo.xml
Index: todo.xml
===================================================================
RCS file: /home/cvs/xml-cocoon2/todo.xml,v
retrieving revision 1.1.1.1.2.5
retrieving revision 1.1.1.1.2.6
diff -u -r1.1.1.1.2.5 -r1.1.1.1.2.6
--- todo.xml 2001/07/12 13:33:42 1.1.1.1.2.5
+++ todo.xml 2001/07/13 09:44:54 1.1.1.1.2.6
@@ -4,7 +4,7 @@
<!--
History of Cocoon changes
- $Id: todo.xml,v 1.1.1.1.2.5 2001/07/12 13:33:42 cziegeler Exp $
+ $Id: todo.xml,v 1.1.1.1.2.6 2001/07/13 09:44:54 cziegeler Exp $
-->
@@ -49,12 +49,6 @@
</action>
<action context="code">
- Check and fix xsl:import which doesn't seem to work expected... very strange..
- it might be an XSLT problem with the XSP example since it uses namespaces
- heavily... should we use the namespace() axis?
- </action>
-
- <action context="code">
Remove deprecated methods from org.apache.cocoon.xml.util and make it clean
for SAX2 final.
</action>
@@ -64,20 +58,31 @@
behavior that cannot work with views.
</action>
+ <action context="code">
+ Complete/write documentation in general.
+ </action>
+
+ <action context="code">
+ Remove the pushURI and popURI methods from the environment.
+ </action>
+
<action context="code">
- Create a form validation Action that uses an external configuration file
- to validate the form and make sure that values are within acceptable ranges.
- IIRC this has beed recently posted to the dev list.
+ 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.
</action>
<action context="code">
- Complete/write documentation in general
+ 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.
</action>
<action context="code">
- Implement an internal profiling tool that should indicate the load and history of
- such along with the status page. Something both useful and fancy to show the
- power of C2.
+ Update and improve the profiling tool from the HEAD cvs and incorporate it
+ into the 2.0 branch.
</action>
</actions>
----------------------------------------------------------------------
In case of troubles, e-mail: [EMAIL PROTECTED]
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
