You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@commons.apache.org by he...@apache.org on 2003/06/07 19:57:17 UTC
cvs commit: jakarta-commons-sandbox/configuration/xdocs tasks.xml
henning 2003/06/07 10:57:17
Modified: configuration/xdocs tasks.xml
Log:
Adding some todo items to the task list
Revision Changes Path
1.2 +17 -1 jakarta-commons-sandbox/configuration/xdocs/tasks.xml
Index: tasks.xml
===================================================================
RCS file: /home/cvs/jakarta-commons-sandbox/configuration/xdocs/tasks.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- tasks.xml 2 Jun 2003 18:01:01 -0000 1.1
+++ tasks.xml 7 Jun 2003 17:57:17 -0000 1.2
@@ -14,7 +14,23 @@
</p>
<subsection name="High priority">
-
+ <ul>
+ <li>Using XML based digester rules will probably blow this bugger
+ apart. You do need a factory from an inner class of the
+ Configuration factory to get the base Path right; even if
+ the test with the rule configuration file works, I'm pretty
+ sure that the resulting rule set will not read configuration
+ files if you're not running from the current (".") directory
+ as base path. This needs more thinking and checking.</li>
+
+ <li>I'm also 99% sure that using XML based Digester rules and
+ Namespace awareness in the configuration file can't be used
+ together. As far as I can see, the namespace awareness must
+ be set/reset before the rules are added. In the case of the
+ DigestLoader (using a DigesterRules() URI), the rules are
+ already added when configureNamespace() is called on the
+ digester. This might even be a bug in the Digester itself.
+ </li>
</subsection>
<subsection name="Medium priority">
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org