hibernate4gwt / News: Recent posts

The new release of hibernate4gwt is available as Gilead 1.2RC1 at
http://gilead.sourceforge.net !

The whole serialization process has been rewritten, improving both
stateless (no more select on merge) and stateful (improved storage
size) modes.

Furthermore, two annotations have been added (@ReadOnly and
@ServerOnly) to help you to control the clone and merge process. With
them, you can prevent sensible data to be sent or modified on client
side.... read more

Releases of Hibernate4GWT are now available on Maven Repository.
To use hibernet4gwt with maven you just have to add this repository

<repository>
<id>hibernat4gwt</id>
<url>http://hibernate4gwt.svn.sourceforge.net/svnroot/hibernate4gwt/maven/</url>
</repository>

and this to your dependency list

<dependency>
<groupId>net.sf.hibernate4gwt</groupId>
<artifactId>hibernate4gwt</artifactId>
<version>1.1.1</version>
</dependency> ... read more

This maintenance release of Hibernate4GWT solves half a dozen bugs, such as :

* Improved selection algorithm for clone operation
* Clone and merge arrays handling
* Fields with private getters were not cloned nor merged
* Association of ProxyClassLoader to each working thread
* Inherited classes where not properly cloned and merged in dynamic proxy and DTO modes
* Class cast exception with collections/maps and bi-directional associations
* Keep ordered collections for clone and merge... read more

This release solves the blocking dynamic proxy class loader issue and use the latest beanlib version for enum clone fix.

This new release of Hibernate4GWT adds some improvements, such as

* Supports UserType
* Supports wrapping objets (ie non persistent instance embedding persistent ones).
* Dynamic proxy code externalisation

It also solves bugs from previous 1.0.4 release, such as merge error after modifying an association on client side, or map merge.

I started a heavy refactoring of the library, so a migration step is needed, which is detailed in the FAQ section.... read more

A fixed version of release 1.0.4 is now available.

Hope this helps !
Bruno

The support for GWT 1.5 M2 suffers of a minor bug for project that do not use JPA annotations at all.
I published a new version of the release (1.0.4b_GWT15_M2) which fix it.
Henceforth, projects that *DO* use annotations need to add the following line in the gwt.xml file, just after the classic 'Hibernate4GWT' inherit line :
<inherits name='net.sf.hibernate4gwt.emul.ejb3.Emul'/>

Bruno

A new distribution of release 1.4, supporting the 2nd milestone of GWT 1.5, is now available in the download section.

Hope this helps !
Bruno

Here is the hibernate4gwt update to support the first milestone of GWT 1.5 !
With it, it is now possible to seamlessly send annotated EJB entities to the GWT, without need of DTO !
Note that for reasons explained at http://www.dotnetguru2.org/bmarchesson/index.php?p=786&more=1&c=1&tb=1&pb=1, hibernate4gwt is still needed if you want to send your entities to the GWT client side...

This solves some important issues (especially on merge) and adds an extended support to Hibernate mappings (see Release notes for details)

I would like to thanks Chris Harris and Andreas Knees that bring a lot of these issues to my attention, for their patience, the tests and their faith in Hibernate4GWT ;-)

A critical bug on collection merge was found to day of the publication of release 1.0.2
Hopefully, it is now corrected and available as a new release (1.0.3).

Sorry for the inconvenience

A new release (1.0.2) is now available. It corrects a ClassLoader issue for GWT-SL(Spring) integration, and the patch submitted by Norman Maurer for ExplicitCloneMapper.

Furthermore, a sample application is now available for each hibernate4gwt configuration (stateless, stateful, Java5 and dynamic proxy). It can be used as a pattern for a new project, or to see "how it works"...

Finally, I wrote a small FAQ for commonly asked questions I used to answer on the library forum or the official GWT one.

The release 1.0.1 is a maintenance one (no API modification) and corrects 3 majors merge bugs :

* Bad session management for merge operation
* Incorrect SecurityException on merge with Java5 support
* "HibernatePOJO not found !" exception when try to merge a new Hibernate POJO with Java native (int, long) ID

Furthermore, this release now includes 2 more ClassMapper implementations (added to the existing DirectoryClassMapper), developped by Florian Siebert and Olaf Kock : an explicit ClassMapper and a multi-directory one.

This release is considered as stable and ready for development use. Note that some refactoring was done and class have been renamed since release 0.5 (such as HibernateLazyManager that became HibernateBeanManager).

It adds dynamic proxy generation for Hibernate beans handling. It means that your POJO will not have to extends LazyGwtPojo anymore, but just implements the standard Java Serializable interface instead !... read more

I published a new release comptabile with the new GWT 1.4 Release Candidate.
Please be careful when selecting the package to download : there is now one for RC1 and another one for RC2.

Bruno

This release brings some important new features :
- Automatic clone and merge : you do not need to clone and merge your Domain class, hibernate4gwt does it for you, just before and after your service call
- Basic Java5 support : Java5 Domain classes are now supported, but need to be explicitely cloned and merged. Nevertheless, cloning is pretty straightforward (no mapping files) and lazy properties are seamlessly handled.... read more

I am currently working hard on the next hibernate4gwt release. Since it has some major improvements, it will probably be a tagged as 0.5.

Here are the planed new features :
- Full support for java.sql dates (Date and Timestamp), meaning JRE emulation and serialization,
- Seamless HibernateRemoteService : clone and merge methods will be executed behind the scene, leaving the RemoteService unaffected by Hibernate POJO handling,
- Automatic naming strategy (the name parameter for merge and clone is no more needed),
- Limited support for Java 5 Hibernate POJO (clone to neutralized DTO and merge from it would be explicitely needed in that case). ... read more

New features :

* Add list support for clone, merge and remove methods of HibernateLazyManager and HibernateRemoteService classes
* Pure POJO support for stateful servers (no more ILazyPojo inheritance needed)

Improvements :

* Documentation update
* A lot of refactoring
* BeanLib version changed (must use release 3.3Beta5)

Bug fixes :

* java.sql.Timestamp RPC serialization exception.
* Warning : because of GWT issue (explained here and here), the Timestamp can only be converted to java.util.Date. Thus, the nanosecond part is lost, so the timestamp cannot be used anymore as a concurrent lock marker !... read more

The documentation has been updated with the help of Nnamdi Jibunoh and is now more complete.

I also just commited a first version of the release 0.2 (available in the SVN repository).
-> ILazyPojo (and LazyGwtPojo) inheritance can now be removed from the domain class. Warning : it works only with a stateful POJO store ! For stateless application, you still have to use the LazyGwtPojo abstract class.
-> I did some kind of refactoring, mainly renaming or moving class to a more appropriate package.... read more

For more details, please refer to http://hibernate4gwt.sourceforge.net