An alpha version of NHibernate 1.2.0 was released today. This release provides a preview of upcoming changes in the next NHibernate release. The most important changes are:

• Support for .NET Framework version 2.0. Generic collections (and any user-supplied collection types) are supported and generic overloads were created for several common methods.
• All classes and collections are now lazily loaded by default (i.e. the default setting for the lazy attribute is now "true"). To aid in the transition, classes used for lazy loading are now validated and an error is thrown if any of their public members are not virtual. This validation can be disabled.
• All assemblies are now signed using a newly generated key which is distributed in the download.

More details about these and other changes can be found in the release notes.
Download the package at Sourceforge.

The download also contains the libraries that were formerly part of NHibernateContrib package - the two packages were merged to make things easier to manage.

Note that this is an alpha-quality release, which means that more breaking changes may occur in future releases. Please report any bugs you find.

Finally, I would like to thank all the contributors who submitted patches to JIRA. Although I applied most of the patches with significant delay and rejected a few, I appreciate your interest in NHibernate and your willingness to contribute.

Good work Sergey!

Looks like you've been busy...

Cheers,

Symon.

congrats from me too.. !

Great! Great time for the release - just adopted generics!...

Keep up the good work!

WOW ! Thats wonderful !!!!!

thank you and congradulations !!!!!!!

Thanks man! :P

Generics rocks!

Hard work! How about nullable? Go ahead.

.NET 2.0 nullable types are supported as well.

Hi,

to make code using the ISession-API more concise and more type safe, the following generic Session.Load method could be incorporated into ISession / SessionImpl :



Usage example:


Instead of:


Regards
Mick

Implemented already.

Great news!

What about a PostLoad method in IInterceptor? I think it would be nice to be able to manipulate an entity right after it was loaded from DB.
The [NH-543] patch adds this feature among other.

I know this can be achieved by having entities implement ILifeCycle but I prefer the interceptor.

Thanks for the update Sergey. Much appreciated, especially the generics and nullables support. I appreciate you applying the SQL Server 2005 patch that I submitted too.

I'm wondering if changing the private/public key isn't going to cause problems though. Please see the following post. I ran into this a little while back and I'm having the same problem when I try using the new alpha. Namely, I can't load BLOB data that was saved with NHibernate 1.0.2.

http://forum.hibernate.org/viewtopic.php?t=959653

As far as I can tell, it looks like what's happening is that an NHibernate class or something is getting serialized into my BLOB field in the database. Then when I try to deserialize it, it's looking for the old version of NHibernate. It works OK, if I switch between 1.0.1 and 1.0.2, but, not if I switch to a version that I built with my own private key, or, with the new alpha.

Is there anyone out there that is using BLOB or CLOB fields that can do a test and confirm that I'm not doing something stupid and there really is a problem? Basically, all you have to do to test it is upgrade to the new alpha version of NHibernate and attempt to load a BLOB field that you saved using on older version of NHibernate.

It looks like I screwed something up in one of my mapping files. I think this might not be an issue. Sorry.

Since Hibernate 3 already implements the same functionality, but in a different way, I'd rather implement it their way than invent our own solution.

Thanks a lot!

Is it now possible to generate Outer Join using Criteria?

Cheers, Tom