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-sandbox/betwixt STATUS.html
Date Thu, 21 Feb 2002 01:19:08 GMT
jstrachan    02/02/20 17:19:08

  Modified:    betwixt  STATUS.html
  Log:
  Updated the to do list with some more stuff we could do - basically to support more complex
mappings and improve documentation.
  
  Revision  Changes    Path
  1.4       +37 -2     jakarta-commons-sandbox/betwixt/STATUS.html
  
  Index: STATUS.html
  ===================================================================
  RCS file: /home/cvs/jakarta-commons-sandbox/betwixt/STATUS.html,v
  retrieving revision 1.3
  retrieving revision 1.4
  diff -u -r1.3 -r1.4
  --- STATUS.html	19 Feb 2002 17:14:24 -0000	1.3
  +++ STATUS.html	21 Feb 2002 01:19:08 -0000	1.4
  @@ -7,7 +7,7 @@
   
   <div align="center">
   <h1>The Jakarta Commons <em>Betwixt</em> Package</h1>
  -$Id: STATUS.html,v 1.3 2002/02/19 17:14:24 jstrachan Exp $<br>
  +$Id: STATUS.html,v 1.4 2002/02/21 01:19:08 jstrachan Exp $<br>
   <a href="#Introduction">[Introduction]</a>
   <a href="#Dependencies">[Dependencies]</a>
   <a href="#Release Info">[Release Info]</a>
  @@ -87,7 +87,42 @@
   
     <tr>
       <td><strong>More complex mappings</strong>. Demonstrate the use of
Betwixt 
  -    with complex Java Bean graphs.</td>
  +    with complex Java Bean graphs.
  +    <p>For example the betwixt file could allow methods to be used in addition 
  +    to bean properties for mapping objects which are not beans. </p>
  +    <p>Also we could support the ContextExpresssion to allow a bean to change 
  +    how its child objects appear. e.g. a Customer object may contain a Map 
  +    property which might appear differently to an Order object which has a Map 
  +    property - depending on the types of the keys and values. So rather than 
  +    relying on Map.betwixt to decide, the Customer.betwixt could specify the XML 
  +    format for the Map object.</p>
  +    <p>Allow betwixt files to be specified explicitly on the Introspector. This 
  +    will allow a Customer.betwixt to be used on a FooBarCustomer bean and to 
  +    allow different views to be used on the same bean. Might also want to 
  +    consider the introspector searching base classes and interfaces so that 
  +    derived types can inherit their parents formatting.</p>
  +    <p>Should check the java.beans.Introspector rules to check we follow them as

  +    closely as possible when finding betwixt files like the bean introspector 
  +    looks for BeanInfo classes.</td>
  +    <td align="center">&nbsp;</td>
  +  </tr>
  +
  +  <tr>
  +    <td><b>Code refactor</b>. There is some repeated code across the

  +    XMLIntrospector and then various classes in the digester package, 
  +    XMLBeanInfoDigester, ElementRule, AttributeRule. The code could maybe be a 
  +    bit cleaner after a refactor to promote reuse and maybe allow some Strategy 
  +    patterns to be used - such as to deduce what are primitive types, loop types 
  +    and so forth.</td>
  +    <td align="center">&nbsp;</td>
  +  </tr>
  +
  +  <tr>
  +    <td><b>Improve digester defaulting</b>. We should try improve the
automatic 
  +    creation of Digester rules by the BeanReader class. Maybe adding some 
  +    configuration details in the betwixt XML document, say an <i>addMethod=&quot;addFoo&quot;</i>

  +    attribute or something. We should maybe deduce all addFoo(Foo foo) methods 
  +    in the default digester.</td>
       <td align="center">&nbsp;</td>
     </tr>
   
  
  
  

--
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