lundi nov. 03, 2008

SDPY - Java Persistence

Three years ago, the Java persistence ecosystem was undergoing big changes. Three years later, JDO as an API is an old story and vendors have morphed into JPA, SDO, etc. TopLink Essentials became EclipseLink, WebSphere is now using OpenJPA, Oracle is replacing TopLink in Oracle WebLogic and JBoss is still the only one shipping with Hibernate.

mercredi oct. 29, 2008

Hibernate in GlassFish - Reloaded

This is a recurring question on the GlassFish forums and mailing lists: "How do can I use Hibernate as a JPA provider in GlassFish?". Mitesh has had this post on the subject up for a little while (some more here) but with the recent release of Hibernate 3.4 made it a little trickier to integrate into GlassFish (NoClassDefFoundError of ReflectionManager seems like a common pattern). Sun's Marina Vatkina has provided an updated list of the JARs needed in the glassfish/lib directory to run Hibernate in GlassFish v2 as a comment to Mitesh's post.

For the record, here are the JAR files required from hibernate-entitymanager-3.4.0.GA and hibernate-distribution-3.3.1.GA :
• antlr-2.7.6.jar
• commons-collections-3.1.jar
• dom4j-1.6.1.jar
• ejb3-persistence.jar
• hibernate-annotations.jar
• hibernate-commons-annotations.jar
• hibernate-entitymanager.jar
• hibernate3.jar
• javassist.jar
• jta-1.1.jar
• log4j.jar
• slf4j-api-1.5.2.jar
• slf4j-log4j12.jar
(from hibernate-entitymanager-3.4.0.GA/lib/test).

lundi nov. 05, 2007

SDPY - JPA

Two years ago, I was commenting on the JPA evolution. 24 months mater, Hibernate is still a very vibrant community, but interestingly enough it's not the default in any Java EE 5 application server (at least until JBoss 5 releases). Clearly developers do use JPA outside the container (for batch or Swing applications), BEA/SolarMetric donated openJPA, and WebSphere "Classic" is still not reported as supporting Java EE 5...

mardi oct. 09, 2007

Hibernate in GlassFish v2

GlassFish comes with TopLink Essentials as the default JPA implementation.
Eskatos has a working solution to replace it with Hibernate 3.3.1 GA. Thanks for sharing!

Hibernate validators and lucene integration are the two most frequently reasons to use Hibernate as the JPA implementation.
Eskatos also reports on IRC that joda-time/hibernate integration is another good reason. Of course, once you use these, your code becomes non-portable across JPA implementations and NetBeans' Verifier (a portability tool based on the AVK) will report failures.

More discussion on a similar topic here.

About

This blog has moved

Alexis Moussine-Pouchkine's Weblog

GlassFish - Stay Connected

Search

Archives
« avril 2014
lun.mar.mer.jeu.ven.sam.dim.
 
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
    
       
Today
Blogroll

No bookmarks in folder

News

No bookmarks in folder