commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From jstrac...@apache.org
Subject cvs commit: jakarta-commons/betwixt/xdocs todo.xml
Date Fri, 14 Jun 2002 04:29:30 GMT
jstrachan    2002/06/13 21:29:30

  Modified:    betwixt/xdocs todo.xml
  Log:
  added other to do list items from recent discussions; also prioritized them
  
  Revision  Changes    Path
  1.6       +28 -7     jakarta-commons/betwixt/xdocs/todo.xml
  
  Index: todo.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/betwixt/xdocs/todo.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- todo.xml	14 Jun 2002 03:42:20 -0000	1.5
  +++ todo.xml	14 Jun 2002 04:29:30 -0000	1.6
  @@ -7,14 +7,19 @@
     </properties>
   
     <body>
  -    <section name="TODO"> 
  +    <section name="TODO list">
         <p>
           The following is a list of items that need to be completed in
           Betwixt.  Contributions are welcome! 
         </p>
         
  +    
  +    <secton name="High priority"> 
         <ul>
           <li>
  +		  If an addFoo() method is found with no matching getFoos() then a warning should be
generated.
  +		</li>
  +        <li>
   		  Currently betwixt causes digester to output a warning '[WARN] Digester - -Empty stack
(returning null)'.
   		  We should patch the way betwixt uses digester to avoid this warning message.
   		</li>
  @@ -22,23 +27,39 @@
   		  Consider allowing the parsing of XML to order the properties/elements in the XMLBeanInfo
   		  so that when the XML is output again it follows the same XML ordering again.
   		  There is an example describing this 
  -		  <a href="http://nagoya.apache.org/eyebrowse/ReadMsg?listName=commons-dev@jakarta.apache.org&amp;msgNo=8488">here</a>
  -		</li>
  -        <li>
  -		  Create a SAXWriter class in the io package that takes a bean and writes to a SAX ContentHandler
  -		  rather that outputting textual XML like BeanWriter does.
  -		  This will allow Betwixt to work nicely in XML pipelining environments like Cocoon and
Jelly.
  +		  <a href="http://nagoya.apache.org/eyebrowse/ReadMsg?listName=commons-dev@jakarta.apache.org&amp;msgNo=8488">here</a>.
  +		  For example we could add a feature to parse the DTD and order the XMLBeanInfo according
to the order in the DTD.		  
   		</li>
           <li>
   		  Improved documentation! Improve package level documentation so that new developers
can get up 
             to speed more quickly. Ensure all betwixt features have good user documentation.

             More good code examples.
           </li>
  +       </ul>
  +    </section>
  +    
  +    <section name="Medium priority"> 
  +      <ul>
  +        <li>
  +		  BeabWriter should have a setEndOfLine() method to allow configurable EOL strings, defaulting
to "\n"
  +		</li>
  +        <li>
  +		  Create a SAXWriter class in the io package that takes a bean and writes to a SAX ContentHandler
  +		  rather that outputting textual XML like BeanWriter does.
  +		  This will allow Betwixt to work nicely in XML pipelining environments like Cocoon and
Jelly.
  +		</li>
  +       </ul>
  +    </section>
  +    
  +    <section name="Low priority"> 
  +      <ul>
           <li>
   		  Create a W3C DOM implementation that acts as a facade on top of beans to allow beans
to 
   		  be transformed in XSLT engines as XML.
   		</li>
          </ul>
  +    </section>
  +    
       </section>
     </body>
   </document>
  
  
  

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>


Mime
View raw message