Velocity Reviews - Computer Hardware Reviews

Velocity Reviews > Newsgroups > Programming > Java > JPO, which is better, using (Entity) Transaction or simple jdbc

Thread Tools

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

Posts: n/a

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?

Thanks lots


Reply With Quote

Thread Tools

Posting Rules
You may not post new threads
You may not post replies
You may not post attachments
You may not edit your posts

BB code is On
Smilies are On
[IMG] code is On
HTML code is Off
Trackbacks are On
Pingbacks are On
Refbacks are Off

Similar Threads
Thread Thread Starter Forum Replies Last Post
JDBC transaction isolation markspace Java 16 05-04-2012 01:58 PM
How to handle JDBC transaction the right way? Java 5 01-27-2006 03:24 AM
oracle.jdbc.OracleDriver vs oracle.jdbc.driver.OracleDriver Betty Java 1 05-21-2005 05:15 PM
Win2003 SP1 error: "New transaction cannot enlist in the specified transaction coordinator" Vencz Istv?n ASP General 2 05-02-2005 05:53 AM
Re: jdbc help:sun.jdbc.odbc.JdbcOdbcDriver Keith Wansbrough Java 0 08-16-2004 07:31 PM