Sunday November 24, 2002
XDoclet and Castor I found this post on the castor-dev mailing list this afternoon. It seems to indicate that there's a better version of the Castor module for XDoclet.
The "exolab2" module is nearly identical to the original exolab module in
that it:
1. generates the mapping.xml file
however, exolab2 differs in that it:
1. works on the fields in a class instead of the methods
-working with field name seems easier and more logical as castor
is for mapping class/db fields, not methods
2. generates the database.xml file
3. generates the create.sql and drop.sql for each class' table
4. doesn't require explicitly declaring the @castor:field-sql type="..." for each class field;
it uses a simple look up .xml file to retrieve the
appropriate/default sql type for
the field's java type
5. doesn't require explicitly declaring the @castor:class table="...";
the class' name will be used as the default table name
so in summary, it generates:
-database.xml
-mapping.xml
-create.sql
-drop.sql
with less "work" than before. basically, these improvements are to help
developers quickly and easily generate all the castor-specific and
non-castor-specific (sql table defintions) code for new projects.
Too bad this isn't available in XDoclet as of yet. Hmmm, maybe I can use Castor Doclet to generate my DDL.
Posted in General
at Nov 24 2002, 09:11:50 AM MST
Add a Comment
Search This Site
Recent Entries
- Secure JSON Services with Play Scala and SecureSocial
- My What's New in Spring 3.1 Presentation
- Twitter's Open Source Summit: Bootstrap 2.0 Edition
- Refreshing AppFuse's UI with Twitter Bootstrap
- 2011 - A Year in Review
- Upgrading AppFuse to Spring Security 3.1 and Spring 3.1
- What have I been working on at Taleo?
- Our Engaging Trip to Paris and Antwerp
- My HTML5 with Play Scala, CoffeeScript and Jade Presentation from Devoxx 2011
- Deploying Java and Play Framework Apps to the Cloud with James Ward