Switch from EclipseLink to Hibernate Persistence Provider

Hi folks !

*News*
Hibernate 3.5 with JPA2.0 support is out since 30 march. The 3.5.1 version
is out since april 15 with few corrections.

The real new is that hibernate search 3.2 is out since may 5, and support
JPA2.0 ! 

We didn't wait for nothing ! A great improvement is coming up on FSNet !

*Now What ?*
So what's is going to happen to our favorite Firm Social Network ? 
It's obvious that a Full Text Search Engine would be a great feature, and
until there nothing was compatible with JPA2.

Thanks to RedHat->JBoss->Hibernate Team and to my hero Emmanuel Bernard we
have all we need to create this feature now.

*Problems*
Hibernate implementation of JPA2.0 deals a little differently from
eclipselink with inherited relations. 
If you have 
- a class A with a property a, 
- a class B extends A
- a class C with a manyToOne on B instances, 
you cannot use a mappedBy("a") if you create a oneToMany relation on the B
class except if you use a SingleTable InheritanceType with a Discriminator
Column.

Until now we used only Table per concrete class. This method privileges
space over performance. The single table inheritance use only one table per
class hirarchy, so columns are often unused but there is not need to
perform joins when fetching instances.

*Solution ?*
I think we could use this method, considering that FSNet is not supposed to
manage thousand of people or interaction.

When we will agree on that, the migration should be quick and we will be
able to work with HibernateSearch

Original issue reported on code.google.com by proucell...@gmail.com on 8 May 2010 at 1:11

jasimcse / fsnet

Switch from EclipseLink to Hibernate Persistence Provider #206