at this point, i definately feel that pure cmp is the way to go (i stared at those ddls for quite some time debating whether or not i wanted to re-write them), but i don't think it's necessary for the 1.1 release.
i do think that if ppl are reworking a module for 1.1 and are comfortable w/ xdoclet, etc then by all means include it, but otherwise i think this should be set as a goal for the 2.0 release. i don't have oracle, mysql, or postgres running at home, so while i haven't had any issues creating tables in hsqldb, i don't know if someone else may have an issue. (i know for hsqldb, i have to set the pk-constraint to false, but this may not be necessary for the other dbs). btw: preloading data could probably be done w/ .bsh scripts that could be lumped into the deployed ear - they'd just need a check to see if the data is already there so it doesn't try to re-create it. View the original post : http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3832634#3832634 Reply to the post : http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3832634 ------------------------------------------------------- This SF.net email is sponsored by: The Robotic Monkeys at ThinkGeek For a limited time only, get FREE Ground shipping on all orders of $35 or more. Hurry up and shop folks, this offer expires April 30th! http://www.thinkgeek.com/freeshipping/?cpg=12297 _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
