Showing messages 1 through 17 of 17.

• Simple JDBC
  2006-10-06 03:59:41 mickd [Reply | View]
  
  With the enhancements coming in JDBC 4.0 (whenever that's due) I can imagine a rise in JDBC usage for simple data access. Read up on how annotations can be used for simple Table-To-JavaBean mapping.

  Another hidden gem that I have enjoyed playing with but never heard of anyone else using is the Apache DBUtils project. This is a nice and easy SqlQuery-To-JavaBean mapping technique. It is easier to use than you might think on first reading the manual. The manual starts by explaining the couple of interfaces that need to be implemented etc, but by the end you will realise that in fact there is surprisingly little to it, and with the pre-rolled implementations there is no need to implement any of it's APIs - just use the classes provided.

  I'm not saying these would replace a full blown ORM tool, but for projects with light sql needs, they might offer a quick and easy way of using (more-or-less) directly JDBC without too much boilerplate coding.

  Now that I think about it, why is there so little obvious use of the standard RowSet classes? Another light way of using JDBC.

• JDO
  2006-10-05 10:59:38 michaelsberga [Reply | View]
  
  This is something that deserves attention. The Specification capability to avoid Database vendor lock-in, not only in terms of database vendor but also in terms of types of databases (RDBM database , OODB database, XML database, etc).
  
  I can say with no doubt, that JDO is the only Persistence specification that meets these requirements.

• Object database
  2006-10-05 08:35:07 jaquinte [Reply | View]
  
  I prefer an Object database. OR mappers are very complicated. You have to learn one extra technology, config files, etc. etc.etc.
  
  We need urgently an powerful open source object database.
• Object database
  2006-10-05 10:13:04 edithr73 [Reply | View]
  
  Here you can find a list of Object Oriented Databases:
  http://www.service-architecture.com/products/object-oriented_databases.html
  
  I prefer those that implement the JDO specification, to avoid vendor lock-in.
  Also note that JDO Specification is the only one that allows migrating easily from an RDBM to an OODB and vice versa.
  I tested my self migrating an small application from Kodo to Versant with no Problem. CAN YOU DO THAT WITH EJB3 or JPA: No you can't.
  
  JDO is, by far the best Persistence specification.

• db4o
  2006-10-04 06:17:29 applebanana8 [Reply | View]
  
  A vote for db4object.

• iBatis SQL Maps
  2006-10-03 14:21:45 djkingcalgary [Reply | View]
  
  Another vote for iBatis SQL Maps. It's a great framework eh?
  
  - Peace

• JPA - Java Persistence API - EJB 3.0
  2006-10-02 06:06:01 pelegri [Reply | View]
  
  I've found that many people are confused about the relationship between these specifications. I suspect your poll results may be affected, but in any case, here is a quick recap.

  JPA is a, non-standard, acronym for Java Persistence API. The specification was developed by the same Expert Group as EJB 3.0 but it is a separate spec. In particular, EJB 3.0 can only be implemented in the context of Java EE 5, while the Java Persistence spec can be implemented in many contexts, including plain Java SE. Unfortunately, when some people say "EJB 3.0", they really mean "Java Persistence".

  There are several implementations of JavaPersistence, including TopLink Essentials (in GlassFish), Hibernate, Kodo and OpenJPA. Some of these implementations may also have other APIs, be for historical reasons or as extensions.

  Hope this helps, - eduard/o

• JPA - Java Persistence API - EJB 3.0
  2006-10-02 06:10:52 pelegri [Reply | View]
  
  Ah, one more. There are two implementations that are often called "TopLink". TopLink Essentials is what is in GlassFish and it implements JavaPersistence. TopLink Essentials was started with a large contribution by Oracle that was based on their shipping TopLink product, which does not support JavaPersistence (to my knowledge). - eduard/o

• JDO
  2006-10-02 02:35:39 martano [Reply | View]
  
  After many tests and comparisons on EJB 2.0 Hibernate and JDO we found JDO as the best choiche for managing persistence in a mean web application. It's faster and less resource intensive than Hibernate or EJB 2.0. I'ts easy to configure for deployment and it's easy to integrate in Netbeans.

• JDO of course
  2006-09-29 12:02:15 alfredogarciaw [Reply | View]
  
  JDO2 is the most mature persistence specification.
  I really can't trust on anything else.

• Apache iBATIS all the way...
  2006-09-29 11:16:00 prime21 [Reply | View]
  
  Hibernate is great, but iBATIS is much simpler and DBAs will love you for using a tool where they can actually see the SQL query and how things are getting mapped.
  
  http://ibatis.apache.org/
  
  -Bryan

• Apache iBATIS all the way...
  2006-09-29 11:15:35 prime21 [Reply | View]
  
  Hibernate is great, but iBATIS is much simpler and DBAs will love you for using a tool where they can actually see the SQL query and how things are getting mapped.
  
  http://ibatis.apache.org/
  
  -Bryan

• Better poll would have been ...
  2006-09-29 09:49:41 ajsoft [Reply | View]
  
  a specification-based poll, and then when you vote for a particular specification which implementation (if any) so would have had options like
  JPA (in general)
  JPA (Hibernate)
  JPA (Kodo)
  JPA (TopLink)
  JDO2 (in general)
  JDO2 (JPOX)
  JDO2 (Kodo)
  IBatis
  OJB
  Castor
  JDBC
  EntityBeans (EJB2)
  others

• OJB - ObjectRelationalBridge
  2006-09-29 09:07:51 lthall [Reply | View]
  
  We have a production WebSphere Struts application running on z/OS. This is a SOX-compliant EPA tracking system that handles multi-million dollar transactions on a daily basis.
  
  For the past three years, OJB has been doing all of our DB2 persistence quite well. The Turbine-managed schema and object model is moderately complex (3-5 NF). We host our development/test environments on Windows and Linux using the same code in JBoss to connect to replicas in hSQLdb, MySQL, and PostgreSQL.
  
  While I am interested in JDO, Hibernate, etc... it is very hard to justify replacing OJB because it works so reliably.

• Spring-Hibernate/Spring-JDBC template
  2006-09-29 08:20:15 vivekbp [Reply | View]
  
  Only reason for prefering Spring-Hibernate -Spring (Hibernate template) does a good job of mapping the lousy Hibernate Exception into more developer-friendly heirarchy of more meaningful exception types.
  
  Ditto for JDBC template ( used for simple Non-ORM DB access). Takes away the pain of SQLException and vendor-specific error codes.
  
  I am surprised that more than 20% still use JDBC. I'm just hoping they use it for Reporting Tools, for summarizing data (group by, sum(), avg() etc.) or such areas left uncovered by the ORM tools (AFAIK).
  
  JDBC is just too heavy and tedious for simple DB access needs. Time someone gave a serious thought to introducing LINQ in Java?

• Choice of three
  2006-09-29 08:03:04 smbell [Reply | View]
  
  I'm a little torn with JPA up there (which is what I voted for). JPA is an API that is implemented by Hibernate and EJB3, so while I'd probably be using Hibernate if I had my choice I'd take care to write to the JPA spec (which would require Hibernate 3.2 of course).
• I prefer Ibatis over Hibernate
  2006-10-06 11:50:50 johnhurt888 [Reply | View]
  
  I prefer Ibatis. It doesn't have issues like Hibernate opensessioninview and lazy-loading issues. SQL is simple, universal. Ibatis gives me good control. Hibernate has HQL, Criteria API, hardcoding sql-like syntax in ugly java code.
  
  Ibatis is far more practical to me.