Hi Zufeng,

My opinion, there are undoubtedly others:

I am not a big fan of Torque for even simple db applications. Just use jdbc, it's not like writing sql is hard or anything. If your application warrants it you can use EJBs instead. There are other object/db mapping tools like Object Bridge that do this better than torque _if_ your object model and db schema don't have too big an impedance miss-match.

I would recommend using connection pooling at the infrastructure level via jndi, that way it is completely out of the application domain and universally managed for everyone on your app server. We also found some serious scaling and performance issues with Torque and switched away from using it even inside of jetspeed, your mileage my vary of course.

For the transactional stuff EJBs come to mind as the obvious J2EE approach ( as long as your transaction needs fit into the flat transaction/OTS model).


-tk



At 12:36 AM 9/18/2003 -0700, Zufeng Huang wrote:
All,

As you know, Jetspeed uses Turbine as its core
framework, and Torque as the persistent layer. I just
took a look at Turbine and Torque, but doubt comes
on...

According to Torque's document online, we can develop
VERY simple database applications, but if I need to
operate several tables during a transaction/at one
time, how to??? Another, it seems Torque doesn't
provide transaction, such as rollback, commit(maybe
it's auto-commit).

Is there any document covers its database connection
pool management? how to use its connection pool?

Finally, I just want to know what's the best way to
develop DB-based applications in Jetspeed. Use JDBC
pool provided by Torque or do it by myself?

thanks,

__________________________________
Do you Yahoo!?
Yahoo! SiteBuilder - Free, easy-to-use web site design software
http://sitebuilder.yahoo.com

---------------------------------------------------------------------
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]



Reply via email to