commons-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From rdon...@apache.org
Subject cvs commit: jakarta-commons/betwixt/xdocs faq.xml tasks.xml
Date Thu, 10 Jul 2003 20:41:19 GMT
rdonkin     2003/07/10 13:41:19

  Modified:    betwixt/xdocs faq.xml tasks.xml
  Log:
  Updated documents.
  
  Revision  Changes    Path
  1.6       +17 -12    jakarta-commons/betwixt/xdocs/faq.xml
  
  Index: faq.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/betwixt/xdocs/faq.xml,v
  retrieving revision 1.5
  retrieving revision 1.6
  diff -u -r1.5 -r1.6
  --- faq.xml	13 Feb 2003 18:41:49 -0000	1.5
  +++ faq.xml	10 Jul 2003 20:41:19 -0000	1.6
  @@ -223,20 +223,25 @@
           </dt>
           <dd>
               Betwixt uses <a href='http://jakarta.apache.org/commons/digester.html'>Digester</a>
for bean
  -            reading. The current implementation adds new <em>Rule</em>s at
run time (which handle 
  -            the reading of child elements). This makes life difficult for any extra <em>Rule</em>s

  -            added by the user before the digestion started.
  +            reading. There are problems integrating the last release with custom digester
rules. 
  +            The CVS HEAD version of betwixt now supports this and so users who need to
do this should 
  +            upgrade.
           </dd>
  +        <dt>
  +          <a name="Why Can't A Read My Bean?">
  +            Why does reading my xml return null?
  +          </a>
  +        </dt>
           <dd>
  -            Extra <em>Rule</em>s added by the user will probably not work as
expected. It may 
  -            be possible to find ways to make them work - but equally well, it may be impossible.
  -        </dd>
  -        <dd>
  -            <em>This is a known limitation.</em>
  -        </dd>
  -        <dd>
  -            Hopefully, this will be addressed in a later release.
  -            Until then, you are recommended to use the mapping mechanisms in Betwixt instead.
  +            Here are some common reasons why this may happen:
  +            <ul>
  +            <li><strong>The class lacks a no-argument construct.</strong>
  +            Betwixt only supports creation of beans with no-argument constructors.
  +            This may be fixed in a future release. (Patches for this gratefully received!)</li>
  +            <li><strong>The class need to be registered at a custom path.</strong>
  +            You may need to use <code>registerBeanRegister(String path, Class beanClass)</code>
  +            to register the class at a particular path.</li>
  +            </ul>
           </dd>
         </dl>
       </subsection>
  
  
  
  1.16      +4 -0      jakarta-commons/betwixt/xdocs/tasks.xml
  
  Index: tasks.xml
  ===================================================================
  RCS file: /home/cvs/jakarta-commons/betwixt/xdocs/tasks.xml,v
  retrieving revision 1.15
  retrieving revision 1.16
  diff -u -r1.15 -r1.16
  --- tasks.xml	15 Apr 2003 21:51:45 -0000	1.15
  +++ tasks.xml	10 Jul 2003 20:41:19 -0000	1.16
  @@ -87,6 +87,10 @@
       <subsection name="Medium priority"> 
         <ul>
               <li>
  +                <strong>Add support for constructors with arguments.</strong>
  +                Currently, only beans with no-argument constructors can be read.
  +            </li>
  +            <li>
                   <strong>Create design documentation</strong>
                   This will help people understand the betwixt design.
               </li>
  
  
  

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


Mime
View raw message