Hibernate4.1 Version Features:

Ø  API for loading by natural identifiers (@NaturalId).

Note: (Unfortunately the above feature was hibernates specific not apply to JPA).

Ø  The ability to provide custom dirty handling.

Ø  Addition of a TenantIdentifierResolver for use with multitenancy in getCurrentSession.

Hibernate4.0 Version New Features:

Ø  Provide support for initial multi-tenancy databases.

Ø  Introduces a ServiceRegistry.

Ø  Redesign SessionFactory Building.

Ø  Clean up of Session opening from SessionFactory.

Ø  Using org.hibernate.integrator.spi.Integrator made integration and auto discovery more desirable.

Ø  Improve to work (Better logging) with i18n and message codes.

Ø  Clean up of deprecated interfaces, methods, etc.

Ø  Preparation for OSGI support
Ø  Jdk1.6 (jdbc4) as baseline.

Hibernate3.6  final Version Features:

Ø  Hibernate Core.

Ø  Hibernate Envers(Easy Entity Relationship).

Ø  Hibernate Entity-managers.

Ø  Hibernate Annotations.

Ø  Hibernate-caches

ü  hibernate-c3p0

ü  hibernate-proxool

ü  hibernate-ehcache

ü  hibernate-infinispan

ü  hibernate-jbosscache

ü  hibernate-oscache

ü  hibernate-swarmcache

Ø   Dropping support for JDK 1.4

Ø  Merging of hibernate-jmx and hibernate-annotations modules into hibernate-core. For those of you using Maven, that means hibernate-core-3.6.0.Final.jar contains annotation and jmx support.

Ø  Improved Type support (HHH-5138 and related issues)

Ø  Change in DTD hosting (HHH-5485)

Ø  Slew of documentation changes, including introducing a new Getting Started Guide

Ø  Several improvements to annotations support for discriminators, column-level read/write expressions, and timestamp versions.

New Envers feature (ValidityAuditStrategy) as an alternative way to write history entries. 

Hibernation Version Features:

Ø  Hibernate Core.

Ø  Hibernate Envers(Easy Entity Relationship).

Ø  Hibernate Entity-managers.

Ø  Hibernate Annotations.

Ø  Hibernate Search engine (Apache Lucien Support).

Ø  JSR 317 (JPA2) support.

Ø  Integration of hibernate-annotations, hibernate-entitymanager and hibernate-envers into the core project. See http://in.relation.to/14172.lace for details

Ø  Added Infinispan as a standard second-level cache. See http://infinispan.blogspot.com/2009/10/infinispan-based-hibernate-cache.html for details

Ø  Improvements to the new second-level caching SPI introduced in 3.3 based on feedback from implementers including Ehcache, Inifinispan and JBoss Cache.

Ø  Far better read only / immutable support.

Ø  Support for JDBC 4 such that Hibernate can be used in JDK 1.6 JVMs and make use of JDBC4-compliant drivers.'

Ø  Support for column-level read/write fragments (HBM only for now)

Ø  Initial support for fetch profiles

Hibernate  final Versions and its release dates.:

1.      Hibernate3.0       final         released Year              31^st Mar, 2005.

2.      Hibernate3.1.3                    released Year             20^th Mar, 2006.

3.      Hibernate3.2.6    GA         released Year               09^th May, 2009.

4.      Hibernate3.3.2    GA          released Year             24^th June, 2009. 

5.      Hibernate3.4.0    GA          released Year             20^th Aug, 2008.

6.      Hibernate3.5       final         released Year              13^th Mar, 2010.

7.      Hibernate3.6       final         released Year              14^th Oct, 2010.

8.      Hibernate4.0       final        released Year             15^th Dec, 2011.

9.      Hibernate4.1       final        released Year             09^th Feb, 2012.

What is an Application Server ?

What is an Application Server ?

Ø Application server is a Server Software comprises of web container,EJB Container and other enterprise services. Via.JNDI naming Services JMS,JTS etc.,

Example of some of Application Servers :

·         Weblogic8.1 / weblogic 10

·         JBoss

·         Sun Server

·         WebSphere(WAS from IBM)

·         GlassFish

What is J2EE

What is J2EE ?

Ø J2EE(java 2 Enterprise Edition) is one of the three Java platform from sun micro system.

            Other two’s are :   (1) J2SE(Java 2 Standard Edition)

                                                 (2) J2ME(Java 2 Mobile Edition)

Ø J2EE is a collection of so many Java based technologies.

Ø J2EE technologies broadly divided into 2 catagories

o   Component technologies

o   Service technologies

Component technologies are :

o   Servlets

o   Jsp

o   EJB(enterprise java beans)

·        Servlets and jsp are know as web technologies

·        EJB is known as distributed technologies

·        A servlet and jsp are web components developed by web component developers

·        EJB’s are develooped by business component developers .EJB’s are knows as business components.

Service technologies are :

o   JMS (Java Messaging Service)

o   JTS (Java Transaction Service)

o   JAAS (Java Authentication and autherisation Service)

o   JNDI (Java Naming and directory Interface)

o   Java Mail

Distributed Architecture

Ø If business objects of a service layer are geographycally dispresed in the network and still communicating with one another such enterprise application is said to be distributed appliaction and is said to have distributed tier architecture

N-tier Architecture

Ø An extension of 3-tier architecture is nothing but n-tier architecture

Ø Service layer is one machine ;data layer in one machine; presentation layer is in morethan one machine.i.e. windows based enterprise application can be 3-tier architecture cannot be ‘n’ tier as presentation layer runs in only one machine as one process.

Ø Web-enabling a 3-tier architectural enterprise application is nothing but making it n-tiered.

3-tier architecture

Ø Physical seperation of service layer(data access layer as well) from the presentation layer is nothing but 3-tier architecturre.

Ø One machine for one machine for service layer( and DAL also) and another machine for presentation layer is the actual physical seperation in this architecture.

Ø 3-tier architecture eliminates client side maintainance.it also makes the clients thin

Ø 3 tier architecture does not make the client 100% thin.

2-tier (Client-server)architecute

     Ø 2-tier architecture is also known as client-server architecture.

Ø In two tier architecture always server is the database server(data layer).

Ø In such physical and data access layer run in one machine which is nothing but client machine.