hi, > I've looked at using the OJB-XDoclet project to do the same type of > thing, but it seems to have some bugs as well. Plus, I prefer to do my > modeling from the DB, and just extend those base classes.
yep, we also have to work with reverse engineering, we are using torque because it gives us much more control on the repository/code generation. we also need to do some automated changes in the repository (after generating it trough torque) before generating the object model. The reverse db tool doesn't give us the possibility to do that and to integrate these steps in ant scripts. > As far as working with 1:n / n:m, I think that we're going to extend > the Torque DTD/schema and add a new possible data type "VECTOR". Then > using the Velocity templates build specialized sections when using this > data type. We've already added some base functionality through the > Velocity templates, but haven't tried this yet. > > Let me know if this approach sounds good to you... yep, i was also thinking to do something similar, however I still hadn't the time to check it deeply (just writing some docu for the project, boooooring) It is probably useful to get a look how the reversedb tool generates the shema for 1:n/n:m relationships by looking in its source code (yeah, I love Open Source) I'm probably going into this in the second half of next week, so if you have some solutions, it would be great if you could post them. Thanks bye danilo --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
