Thank you for your responses.
I know a bit of Xdoclet, so i will take a look on it.
you will have feedback soon.
Regards, Enrique.
-----Mensaje original-----
De: tek1 [mailto:[EMAIL PROTECTED]]
Enviado el: miercoles, 18 de septiembre de 2002 5:08
Para: [EMAIL PROTECTED]
Asunto: Re: [castor-dev] Generate Database
hi enrique.
see my below post that i sent to the xdoclet team. if you're familiar with
xdoclet and interested in working together, please let me know.
the xdoclet team said that they won't be able to add it now, as they're
working very hard to get xdoclet1.2 released. however, we can work on the
castor part together while were waiting for xdoclet1.2 to be released.
would also like to work on integrating it with castordoclet, if possible,
so that we work together, do more, and create an awesome module.
----
To: [EMAIL PROTECTED]
Cc: Mickael Guessant <[EMAIL PROTECTED]>,Bruce Snyder
<[EMAIL PROTECTED]>
Message-id: <[EMAIL PROTECTED]>
MIME-version: 1.0
Subject: [Xdoclet-devel] Re: [Xdoclet-user] new castor module
Date: Tue, 10 Sep 2002 16:42:45 -0400
Status:
hello xdoclet team!
recently, i've been working on a new version of the castor module and would
like to contribute what i've done so far. it's in the very early stages,
but works to a certain extent and i will continue working on it as much as
i can (sometimes i get very busy though).
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.
what it doesn't handle yet:
1. class references
2. collection usage
3. etc...
(only handle simples java types right now)
what needs improving:
1. mapping.xml formatting
-the formatting of the mapping.xml is terrible
-i wrote the template, such that it's easy to understand, but the output bites
-i previously asked on the ml about removing white space
and handling formatting a little
while back and read a reply that xdoclet's future move
to velocity would solve the
problem; so hopefully the formatting issue will be solved then
-despite the awful look of the mapping.xml, it works.
2. location of some code
-as i was just learning the new xdoclet structure, i
accidentally put some of the changes
in the core package, instead of everything in the
modules, so some cleanup is needed.
-i have include a list of the changes in the attached .zip
file, so recommendations on
where to move the code would be appreciated from some of the more experience
xdoclet developers.
3. documentation
-i was just trying to get something up and working
quickly, so didn't update the previous
castor documentation on how to use it and its new features
4. extensibility
-just wondering how the design might be improved to a more generic subtask
(i.e. "ormapping" subtask) that includes a parameter
like "framework='xxx'" in the
ant target, so that one could generate the mapping and create.sql/drop.sql files
for various framework (i.e. "castor", "objectbridge", etc.)?
-since that may be more than i can handle right now, perhaps we can just start
with the castor implementation and then refactor later to handle other
frameworks...?
i've attached the exolab2 module (directory) and a .zip file of the changes
made to the xdoclet core.
looking forward to possibly working with some of you on improving the module.
thank you.
---
At 19:39 02/09/17 +0200, you wrote:
>Hi all,
>
>I am using Castor Source Generator, Castor XML and now I star with Castor JDO.
>
>I thing all is great, but i miss one thing, generate de database using the
>xsd file of Castor Source Generator.
>
>Is there any tool that do similar operation???
>
>Is there planing to so something like this???
>
>Thank you very much.
>
>Regards, Enrique.
-----------------------------------------------------------
If you wish to unsubscribe from this mailing, send mail to
[EMAIL PROTECTED] with a subject of:
unsubscribe castor-dev
