|
Sponsored Links
Resources
Enterprise Java
Research Library
Get Java white papers, product information, case studies and webcasts
|
News
News
News
|
Messages: 6
Messages: 6
Messages: 6
Printer friendly
Printer friendly
Printer friendly
Post reply
Post reply
Post reply
XML
XML
XML
|
 |
Hibernate 3.2 released, certified JPA compatible
JBoss has released Hibernate 3.2, their popular persistence engine, now certified compliant with the Java Persistence API. In addition to JPA compliance, hibernate adds new query capabilities, declarative data filters, and optimistic locking in a cluster with JBoss Cache.
The Hibernate 3.2 release includes:- Hibernate Core is the full featured, high performance object/relational persistence and query service that popularized object/relational mapping for Java. Hibernate relieves developers from 95 percent of common data persistence related programming tasks, compared to manual coding with SQL and the JDBC API. Hibernate Core offers a powerful native data management and query API, and object/relational mapping with XML metadata. Hibernate Core requires JDK 1.3 or greater and works with any J2EE 1.4 or Java EE 5.0 application server.
- Hibernate Annotations offers several packages of JDK 5.0 code annotations that developers can use to map classes, as a replacement or in addition to XML metadata. Hibernate Annotations supports standard Java Persistence object/relational mapping annotations, native Hibernate extension annotations, and declarative data integrity rule definition and validation with the Hibernate Validator framework. Hibernate Annotations requires JDK 5.0.
- Hibernate EntityManager implements the Java Persistence programming interfaces, object lifecycle rules, and query options as defined by Java Specification Request 220 (EJB 3.0). Combined with Hibernate Annotations, this wrapper offers a complete Java Persistence provider on top of the mature and powerful Hibernate Core. The Hibernate Java Persistence provider is the default Java Persistence provider of the JBoss EJB 3.0 implementation. Additionally, it can be used inside any other Java EE 5.0 application server or standalone with JDK 5.0.
|
|
|
Message #220447
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Hibernate 3.2 released, certified JPA compatible
Congrat for the finally releases of 3.2.
It is much to be hoped, that some existing minor (but sometimes a little bit painful) problems of Annotations and JPA are now solved with 3.2 ...
Hibernate and JPA, Annotations rocks ...
Roland
SOA Kompetenznetzwerk
Information & Collaboration Portal
New Look & Feel and advanced Information- & Collaboration Strategy are upcoming, soon ...
|
|
|
Message #220521
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Hibernate 3.2 released, certified JPA compatible
For JPA, which is better, Hibernate or Toplink Essentials?
What are the differences between the two as it relates to JPA?
Which works better with Derby?
Mike
|
|
|
Message #220523
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Hibernate 3.2 released, certified JPA compatible
Excellent news, congrats to the Hibernate team.
|
|
|
Message #220526
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Hibernate 3.2 released, certified JPA compatible
For JPA, which is better, Hibernate or Toplink Essentials?
In my experience, Hibernate. Although Toplink does seem to be a functional implementation of the spec, what we found was that if something in the spec was marked as 'optional' (and some of these 'optional' features are quite useful) then Toplink essentials probably didn't support it, whereas Hibernate did.
I guess if you want to remain entirely portable then you don't want to be using optional features, but working around the gaps in the implementation in a portable way can be lots of extra work for the developer.
The features in Hibernate became so important for us that we actually replaced the default Toplink based EntityManager with Hibernate in Glassfish.
YMMV.
|
|
|
Message #220533
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Hibernate 3.2 released, certified JPA compatible
For JPA, which is better, Hibernate or Toplink Essentials?
In my experience, Hibernate. Although Toplink does seem to be a functional implementation of the spec, what we found was that if something in the spec was marked as 'optional' (and some of these 'optional' features are quite useful) then Toplink essentials probably didn't support it, whereas Hibernate did.
I guess if you want to remain entirely portable then you don't want to be using optional features, but working around the gaps in the implementation in a portable way can be lots of extra work for the developer.
The features in Hibernate became so important for us that we actually replaced the default Toplink based EntityManager with Hibernate in Glassfish.
YMMV.
Which optional features are you referring to?
Mike
|
|
|
Message #220558
Post reply
Post reply
Post reply
Go to top
Go to top
Go to top
|
|
Re: Hibernate 3.2 released, certified JPA compatible
The JPA spec describes some features as being optional (implementations are not required to support them), but there are also a number of features that are not yet included in JPA but that are still useful to some users. These will hopefully be included in future versions of the spec.
The point is that the EJB 3.0 expert group had to try to decide on and describe the most useful features to standardize to satisfy the most people. Being the Reference Implementation of JPA and on the same release schedule as the spec, TopLink Essentials had to follow the same kind of plan and we chose to support the features that we saw as being the most important, some of which were listed as optional and some of which were not mentioned in the spec at all. Some of these features are supported by Hibernate and some are not. Likewise there are some features that Hibernate feels are important value add for its customers that we do not share.
This thread is supposed to be dedicated to celebrating the fact that Hibernate has now achieved JPA compliance, allowing people to write the same code in Hibernate to work on any JPA vendor, not to highlight the non-standard features between implementations.
Congrats to the Hibernate team for reaching this milestone.
Doug Clarke
Product Manager
Oracle TopLink JPA
|
|
|
| New content on TheServerSide.comNew content on TheServerSide.comNew content on TheServerSide.com |
|
|
Reza Rahman explores the features of the proposed JSR 299, Contexts and Dependency Injection for Java EE (CDI). When approved, it promises to be a key feature of Java EE 6.
(November 2, Article)
SAML is an XML-based standard for exchanging authentication and authorization data between security domains. The single most important problem that SAML was created to solve is the Web browser Single Sign-On problem. Many organizations are debating whether to stay with version 1.1 or move to 2.0. This article makes observations about both options.
(September 28, Article)
Joe Ottinger takes a look at how people learn, and applies it to the practice of programming. He notes that understanding how people learn is an essential part of working in a programming team.
(September 22, Article)
Stephen Maryka gave us an article about the Asynchronous Web and posed a number of questions that get examined like an approach to delivering Asynchronous Web capabilities through extensions to existing Java EE technologies.
(July 14, Article)
JavaServer Faces Flex goal is to provide users capability in creating standard Flex components, part of flexSDK which is open sourced through MPL license, as normal JSF components. This article by Ji Hoon Kim will provide an overview of creating a simple multilingual JSF page consisting of JSF Flex tags.
(June 29, Article)
In this session Jeff explores the key characteristics of successful SOA projects. He covers some of the patterns, and anti-patterns, tool sets, and strategies that he himself learned the hard way. Last, he provides a strategy and blueprint for achieving a high likelihood of success in your SOA project.
(June 23, Tech Talk)
Ari Zilka, CTO of Terracotta, Inc., talks about the new features in Terracotta 3.1, announced during JavaOne and available now.
(June 15, Tech Talk)
In this Tech Talk, Josh Long explores an integration challenge using Spring Integration and walks through the implementation, employing and expanding on the basic patterns of Enterprise Application Integration to tie together components into a function integration solution, and then demonstrates how Spring Integration helps address the integration requirements.
(June 15, Tech Talk)
In this Tech Talk, David Geary teaches you: The basics of Google Web Toolkit; How to implement Ajax-enabled applications in Java; Internationalization; Hooking into the browser history mechanism; Remote procedure calls.
(June 4, Tech Talk)
Jon Kern discusses the best architecture/technical solutions and ensure that they are repeated by all developers. By tackling the architecture up-front in a serial manner, subsequent parallel development will be much more manageable and predictable.
(May 28, Tech Talk)
This keynote describes the frustrations of modern knowledge workers in their quest to actually get some work done, and solutions for how to guard yourself against all those distractions. Neal Ford talks about environments, coding, acceleration, automation, and avoiding repetition as ways to defeat the misguided attempts to sap your ability to produce good work.
(May 26, Tech Talk)
Gil demonstrates how new, aggressive uses of already abundant compute capacity by common applications offer competitive value for application designers.
(May 21, Tech Talk)
Chris Keene introduces WaveMaker as a new way to automate the ability to generate Hibernate classes in order to more quickly bring OR mapping into an application.
(May 19, Article)
In this session Nati Shalom demonstrates how to take a standard Java EE web application and scale it out or down dynamically without changes to the application code. Seeing as most web applications are over-provisioned to meet infrequent peak loads, this is a dramatic change because it enables growing your application as needed, when needed, without paying for unutilized resources.
(May 19, Tech Talk)
Mastering EJB was one of the original and most influential EJB books in the industry. Mastering EJB III now returns with two new expert co-authors, updated for EJB 2.1 and 30% new chapters including security, integration, best practices, open source, and more.
(Book PDF Download)
The Application Server Matrix is a detailed listing of J2EE vendors and their application server products, with information on latest version numbers, J2EE spec support and licensing, pricing, platform support, and links to product downloads and reviews.
(Application Server Comparison Matrix)
|
|
