JPO, which is better, using (Entity) Transaction or simple jdbc

J

John_Woo

Hi,

I'm going to design the database access part of a project, and not
supposed to use EJB. Traditoinally we can use DAO, by using EJB 2 or
just simple JDBC with native SQL.

Recently I found JPO (Java persistent object) has introduced widely,
along with SUN's persistent package. JPO basically implemented by
javax.persistence package, namely getting Transaction
to talk to database

I'm wondering, interms of simplicity of coding, possibilities of
allowing multi-transaction/threadings and performance, can any one tell

which is better using (Entity) Transaction or regula JDBC?
 

Ask a Question

Want to reply to this thread or ask your own question?

You'll need to choose a username for the site, which only take a couple of moments. After that, you can post your question and our members will help you out.

Ask a Question

Members online

No members online now.

Forum statistics

Threads
473,994
Messages
2,570,223
Members
46,813
Latest member
lawrwtwinkle111

Latest Threads

Top