jstrachan 2002/06/07 00:56:39
Modified: betwixt/xdocs faq.xml
Log:
Updated the FAQ to include the recent discussion on betwixt versus JAXB / Castor
Revision Changes Path
1.2 +30 -0 jakarta-commons-sandbox/betwixt/xdocs/faq.xml
Index: faq.xml
===================================================================
RCS file: /home/cvs/jakarta-commons-sandbox/betwixt/xdocs/faq.xml,v
retrieving revision 1.1
retrieving revision 1.2
diff -u -r1.1 -r1.2
--- faq.xml 6 Jun 2002 14:31:29 -0000 1.1
+++ faq.xml 7 Jun 2002 07:56:39 -0000 1.2
@@ -29,6 +29,11 @@
Why is this called Betwixt?
</a>
</li>
+ <li>
+ <a href="#comparison">
+ How does Betwixt compare to technologies like JAXB and Castor?
+ </a>
+ </li>
</ol>
<p><strong>Building Betwixt</strong></p>
<ol>
@@ -67,6 +72,31 @@
</dd>
</dl>
+ <dl>
+ <dt>
+ <a name="comparison">
+ How does Betwixt compare to technologies like JAXB and Castor?
+ </a>
+ </dt>
+ <dd>
+ Where JAXP and Castor are strong is when you have a well
agreed schema (XML
+ Schema for Castor or a DTD in the case of JAXB, last time I
looked) and want
+ to auto-generate beans for parsing and processing the XML.
+ </dd>
+ <dd>
+ Betwixt is strong is when you've already got the beans and
just want a nice
+ looking XML format to serialize/deserialize your beans.
+ Indeed with Betwixt you can just write your beans and not even
worry
+ about XML schemas and providing you follow a simple bean
naming convention
+ (the use of getter, setter and <i>adder</i> methods) you'll
get nice looking XML for free.
+ <dd>
+ </dd>
+ In JDK1.4 there is a
+ <a
href="http://java.sun.com/j2se/1.4/docs/guide/beans/changes14.html";>long term bean
serialization</a>
+ mechanism which you can use. However Betwixt generates cleaner
looking XML which can be customized
+ to your own look and feel. Long term bean serialization
doesn't generate nice looking XML.
+ </dd>
+ </dl>
</section>
<section name="Building Betwixt">
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
