I need to have the many-to-many relantionship properly set in the xml schema file for the torque generation engine, but once it is it works like charm.
And with the experience I was able to write some tuned sql statements although Torque lacks of support for stored procedures and triggers. However, I think I will stick with Torque and encourage everyone to use it with Struts. Thanks for the quick response, -----Mensaje original----- De: Mark Lowe [mailto:[EMAIL PROTECTED] Enviado el: Jueves, 03 de Junio de 2004 12:02 p.m. Para: Struts Users Mailing List Asunto: Re: Why not Torque? I've used torque and hibernate. Torque gets you up and running very quickly, and has less files to maintain (mapping files) . In the case of hibernate to get around the mapping file maintenance a lot of folk including me use xdoclet. Hibernate gives you more control than Torque but has all that messing around to get it running at first to get everything right. I don't remember how torque deals with many-to-many relationships. I believe that the transaction management is probably better with hibernate. But I haven't use torque in a while so i could be wrong. A big difference is that torque has a table based api, where hibernate has a stronger bias towards Objects. I'll have to give torque another go to have a better idea, but your question "Why not torque?" is as good a reason as any to stick with it. Mark On 3 Jun 2004, at 16:35, Julio Cesar De Salvo wrote: > Hi, > I ‘ve been using Torque with Struts for quite a while and > performs very well. > But I’ve seen that you guys usually uses Hibernate with > Struts. > Can you tell me what are the dis/ad vantages. > > Thanks > > Julio Cesar De Salvo - Project Leader > iTechnology S.R.L. - Ciudad de la Paz 2846 - piso 1 > Tel 54 11 4782.6901 / Fax 54 11 4782.6901 > <mailto:[EMAIL PROTECTED]> [EMAIL PROTECTED] > AVISO DE CONFIDENCIALIDAD. La información incluida en este e-mail está > dirigida únicamente al destinatario. Puede contener información > privilegiada, confidencial y que no debe ser revelada. Si ha recibido > este e-mail por error, por favor no disemine, utilice, publique, > distribuya, revele o copie esta comunicación de ningún modo. En cambio, > por favor notifíquenos inmediatamente remitiéndonos este e-mail > (incluso > el mensaje original en su contestación), por fax (54-11-4782-6901) o > teléfono (54-11-4782-6901) y entonces elimine y deseche todas las > copias > de este e-mail. Gracias. > CONFIDENTIALITY NOTICE. The information in this e-mail is intended for > the designated recipient only. It may contain information that is > privileged, confidential and exempt from disclosure. If you have > received this e-mail in error, please do not disseminate, use, publish, > distribute, disclose or copy this communication in any way. Instead, > please notify us immediately by return e-mail (including the original > message in your reply), by fax (54-11-4782-6901) or by telephone > (54-11-4782-6901) and then delete and discard all copies of this > e-mail. > Thank you. > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
