Thanks to Quinton's updated HOWTO I successfully extended TurbineUser which solves my primary key-grabbing issues (thanks for everyone's input along the way). Quinton, a few suggestions if you have the time.
The current HOWTO leaves one with an application that cannot be deployed anew w/ 'ant init' (e.g. to a fresh machine/database straight out of a project cvs repository) -- the howto doesn't go all the way and communicate to users a safe mechanism for inclusion of TURBINE* tables into projectname-schema.xml so they they are auto-generated as part of the sql generation phase but don't manage to funk-up the OM class generation. Perhaps Torque currently can't do this cleanly? Not sure I understand the process enough to tell. I also now have a hand-added field in my extended user class that appears _nowhere_ in my carefully crafted object model xml file; this to me seems a Bad Thing. Is there a way to have my cake and eat it too -- to extend user AND auto-generate viable turbine_* tables and maintain homogeneity b/t object model and database structure? Again, Quinton, thanks for taking one for the team and writing that up; the help was invaluable and in the end the hardest part of the process was realizing that my java/perl-addicted fingers had typed a ';' at the end of my re-declarations in TurbineResources.properties which results in some rather nasty Class not found errors. Fun! -j ------------------------------------------------- James Diggans Bioinformatics Programmer Gene Logic, Inc. Phone: 301.987.1756 FAX: 301.987.1701 -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
