iBATIS is very slick and simple. However it does make you work hard when you need to support different databases. E.g. you cannot have the same insert statement work in both SQL Server and Oracle. You can write complicated SQL and map it with iBATIS, but if you have to generate SQL statements on the fly iBATIS's support for this is not easy. I think you would have to go with straight JDBC calls in such cases, which is possible because you can get the connection from iBATIS.
-----Original Message----- From: Tomáš Procházka [mailto:[EMAIL PROTECTED] Sent: Sunday, April 16, 2006 6:46 AM To: [email protected] Subject: Torque and iBATIS Hi. I have two questions. For what is Torque better and for what iBATIS? Why Apache has two similar projects? And why Torque use this: xercesImpl-2.6.2.jar xml-apis-2.0.2.jar I this need in Java 1.5? A try delete it and all works. Thanks you. -- Tomas Prochazka --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -------------------------------------------------------- NOTICE: If received in error, please destroy and notify sender. Sender does not waive confidentiality or privilege, and use is prohibited. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
