Date: 2005-02-07T20:30:55
   Editor: WendySmoak
   Wiki: Jakarta Commons Wiki
   Page: Digester/TODO
   URL: http://wiki.apache.org/jakarta-commons/Digester/TODO

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -80,7 +80,7 @@
 
 === Add Missing XML Rules ===
 
-There are some Rules that could be configured with xml-based rules, but they 
aren't in !DigesterRuleParser nor the DTD.
+There are some Rules that could be configured with xml-based rules, but they 
aren't in !DigesterRuleParser or the DTD.
 
      !CallMethodRule with 'target stack offset'
      See: 
http://www.mail-archive.com/commons-user%40jakarta.apache.org/msg10012.html
@@ -200,11 +200,16 @@
 Class !DigesterRuleParser in the xmlrules package uses the deprecated begin() 
and end() methods (as do some other rules). Fix these. In general, get rid of 
use of deprecated methods.
 
 === Think about parsing multiple documents ===
+
 Some people have expressed the desire to use the same Digester instance to 
parse multiple xml documents. This is currently (v1.6) fairly unsafe. 
 
 In the current (1.6) version, the best option is probably to create a 
configured Rules object and a configured !SAXParser object and keep these 
cached for reuse but recreate a new Digester object each time. At the least we 
should carefully document what objects are safe for reuse and which are not. 
And what the implications of using Digesters and Rules objects in multithreaded 
apps. I also think the APIs for preconfiguring Rules or !RuleSet objects and 
then reusing them are rather inconsistent, and need some review/fixing. This is 
particularly important for the !XmlRules stuff, as parsing an xmlrules config 
file is not a quick process.
 
 See bugzilla #29428 for some discussion of this.
+
+=== Make the XML Rules DTD more consistent ===
+
+Some things are hyphenated, some are not. One tag uses attr-name while the 
rest use attrname.  One uses prop-name and another propertyname.
 
 == Possible ==
 

---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to