You are viewing a plain text version of this content. The canonical link for it is here.
Posted to xindice-dev@xml.apache.org by vg...@apache.org on 2003/09/04 14:19:27 UTC
cvs commit: xml-xindice status.xml
vgritsenko 2003/09/04 05:19:27
Modified: . status.xml
Log:
4 space indent
Revision Changes Path
1.9 +82 -82 xml-xindice/status.xml
Index: status.xml
===================================================================
RCS file: /home/cvs/xml-xindice/status.xml,v
retrieving revision 1.8
retrieving revision 1.9
diff -u -r1.8 -r1.9
--- status.xml 16 Aug 2003 02:26:03 -0000 1.8
+++ status.xml 4 Sep 2003 12:19:27 -0000 1.9
@@ -2,87 +2,87 @@
<?xml-stylesheet type="text/xsl" href="./tools/antipede/resources/stylesheets/status.xsl"?>
<status>
- <developers>
- <person name="Vladimir Ritz Bossicard" email="vladimir@apache.org" id="VBO"/>
- <person name="Vadim Gritsenko" email="vgritsenko@apache.org" id="VG"/>
- </developers>
- <todo>
- <actions priority="high">
- <action context="xml" dev="open">
- <strong>Compressed DOM: Huge document support</strong> We need to
- create a virtualized byte array class to drive the compressed DOM
- system. Right now, there's a single byte array that represents the
- entire compressed document, but if that byte array is huge, and the
- document doesn't need to be fully traversed, then most of it is
- hanging around in memory for no reason.
- </action>
- <action context="xml" dev="open">
- <strong>Basic Document-level transactions</strong> We need to provide
- the ability to lock a node (and recursively everything beneath it) to
- support node-level transactions. This locking should allow for both
- single writer/many reader and exclusive locking.
- </action>
- <action context="xml" dev="open">
- <strong>Scheduling</strong> An Application-level scheduler needs to be
- developed for performing automated management tasks. Events will fall
- into several classes, including XMLObject method calls and external
- command execution.
- </action>
- <action context="xml" dev="open">
- <strong>The Query Engine</strong> The query engine has basic
- functionality right now. Indexing and XPath query work against a
- Collection, but no unified cross-Collection query system currently
- exists.
- </action>
- <action context="xml" dev="open">
- <strong>Grouped resource-level transactions</strong> A system needs to
- be designed that allows transactions across a set of resources to be
- performed.
- </action>
- <action context="xml" dev="open">
- <strong>XQuery support</strong> The Xindice projects needs to work
- with the Xalan project in order to produce a common Apache Foundation
- XQuery implementation.
- </action>
- </actions>
- <actions priority="medium">
- <action context="code" dev="open">
- <strong>Specifications</strong> We need to continue fleshing out our
- technical specifications for the core.
- </action>
- <action context="code" dev="open">
- <strong>Javadocs</strong> We need to continue fleshing out our technical
- specifications for the core.
- </action>
- </actions>
- </todo>
+ <developers>
+ <person name="Vladimir Ritz Bossicard" email="vladimir@apache.org" id="VBO"/>
+ <person name="Vadim Gritsenko" email="vgritsenko@apache.org" id="VG"/>
+ </developers>
+ <todo>
+ <actions priority="high">
+ <action context="xml" dev="open">
+ <strong>Compressed DOM: Huge document support</strong> We need to
+ create a virtualized byte array class to drive the compressed DOM
+ system. Right now, there's a single byte array that represents the
+ entire compressed document, but if that byte array is huge, and the
+ document doesn't need to be fully traversed, then most of it is
+ hanging around in memory for no reason.
+ </action>
+ <action context="xml" dev="open">
+ <strong>Basic Document-level transactions</strong> We need to provide
+ the ability to lock a node (and recursively everything beneath it) to
+ support node-level transactions. This locking should allow for both
+ single writer/many reader and exclusive locking.
+ </action>
+ <action context="xml" dev="open">
+ <strong>Scheduling</strong> An Application-level scheduler needs to be
+ developed for performing automated management tasks. Events will fall
+ into several classes, including XMLObject method calls and external
+ command execution.
+ </action>
+ <action context="xml" dev="open">
+ <strong>The Query Engine</strong> The query engine has basic
+ functionality right now. Indexing and XPath query work against a
+ Collection, but no unified cross-Collection query system currently
+ exists.
+ </action>
+ <action context="xml" dev="open">
+ <strong>Grouped resource-level transactions</strong> A system needs to
+ be designed that allows transactions across a set of resources to be
+ performed.
+ </action>
+ <action context="xml" dev="open">
+ <strong>XQuery support</strong> The Xindice projects needs to work
+ with the Xalan project in order to produce a common Apache Foundation
+ XQuery implementation.
+ </action>
+ </actions>
+ <actions priority="medium">
+ <action context="code" dev="open">
+ <strong>Specifications</strong> We need to continue fleshing out our
+ technical specifications for the core.
+ </action>
+ <action context="code" dev="open">
+ <strong>Javadocs</strong> We need to continue fleshing out our technical
+ specifications for the core.
+ </action>
+ </actions>
+ </todo>
- <changes>
- <!-- Add new releases here -->
- <release version="1.1-dev" date="August 6 2003">
- <action dev="VG" type="fix" fixes-bug="17035">
- JDK 1.4 works with Xindice and it is supported.
- </action>
- <action dev="VG" type="fix">
- Collection meta data now has correct collection creation time.
- </action>
- <action dev="VG" type="update">
- Added XINDICE_DB_HOME environment variable and corresponding
- xindice.db.home system property. This property takes precedence
- over db location preferred by the driver (XindiceServlet prefers
- WEB-INF folder and embedded driver prefers directory where
- system.xml file is located).
- </action>
- <action dev="VG" type="update">
- Update ant to version 1.5.3 and move it into tools/ant/.
- Build script modified to call ant script instead of ant class.
- Compilation from the Cygwin environment now working.
- </action>
- </release>
- <release version="1.1b" date="11/1/2002">
- <action dev="VBO" type="add" context="admin">
- Xindice has a new website.
- </action>
- </release>
- </changes>
+ <changes>
+ <!-- Add new releases here -->
+ <release version="1.1-dev" date="August 6 2003">
+ <action dev="VG" type="fix" fixes-bug="17035">
+ JDK 1.4 works with Xindice and it is supported.
+ </action>
+ <action dev="VG" type="fix">
+ Collection meta data now has correct collection creation time.
+ </action>
+ <action dev="VG" type="update">
+ Added XINDICE_DB_HOME environment variable and corresponding
+ xindice.db.home system property. This property takes precedence
+ over db location preferred by the driver (XindiceServlet prefers
+ WEB-INF folder and embedded driver prefers directory where
+ system.xml file is located).
+ </action>
+ <action dev="VG" type="update">
+ Update ant to version 1.5.3 and move it into tools/ant/.
+ Build script modified to call ant script instead of ant class.
+ Compilation from the Cygwin environment now working.
+ </action>
+ </release>
+ <release version="1.1b" date="11/1/2002">
+ <action dev="VBO" type="add" context="admin">
+ Xindice has a new website.
+ </action>
+ </release>
+ </changes>
</status>