NHibernate.Validator for NHibernate 3.2

[chetan chaphekar]

Dear Sir,

I am not able to find NHibernate.Validator for NHibernate 3.2. Current version is available for NHibernate 3.1.

How can i use it my project. Please help me.

Regards
Chetan Chaphekar

[allan....@gmail.com]

Get it from SVN and build it against 3.2. It works fine.

The SVN repository is located at
https://nhcontrib.svn.sourceforge.net/svnroot/nhcontrib/trunk/src/NHibernate.Validator

[Chris Bohling]

Even though the suggestion works, the NuGet release of NHibernate.Validator needs to be updated to support the version of NHibernate (3.2) available through NuGet. I've lost a lot of time dealing with this incompatibility.

[Morten Brix Pedersen]

Hello Allan,

It does not work "fine". Actually, it does not compile due to removed
ProxyFactoryFactoryNotConfiguredException in this method:

public static bool IsProxyFactoryConfigurated()
{
try
{
var f =
NHibernate.Cfg.Environment.BytecodeProvider.ProxyFactoryFactory;
return true;
}
catch (ProxyFactoryFactoryNotConfiguredException)
{
return false;
}
}

Is NHibernate.Validator project dead?

- Morten.

On 23 Sep., 19:20, "allan.ritc...@gmail.com" <allan.ritc...@gmail.com>
wrote:

> Get it from SVN and build it against 3.2.  It works fine.
>

> The SVN repository is located athttps://nhcontrib.svn.sourceforge.net/svnroot/nhcontrib/trunk/src/NHi...

[Ricardo Peres]

The group for NHibernate Contrib is http://groups.google.com/group/nhcdevs.

[Jason Meckley]

@chris, do you have a patch? if not please don't criticize what is lacking. this project only thrives because of the volunteers who keep it going. no one is paid to maintain NH, or owes anyone anything.

you are welcome to supply a patch for the nuget issue, but don't just demand it be updated because you were inconvenienced.

[allan....@gmail.com]

Sorry, I had to make one change to get it to compile. I had to comment
out the missing exception class. It now compiles fine and works
against 3.2.

[Valeriu Caraulean]

I've asked in NHContrib group if the NH.Validator's (and NHContrib) source will be available on GitHub but nobody answered. I'm sure that making it available on github or somewhere else (in a DVCS) will allow people if not contribute directly but at least fixing issues for themselves and have them public in their forks.

I also have a patch in my local repository (Mercurial) that makes it work with NH 3.2. I feel sorry, but creating & sending path to an SVN repo without any chance to have it integrated rapidly in the main line is too much hassle...

On Thu, Nov 17, 2011 at 7:06 PM, Jason Meckley <jasonm...@gmail.com> wrote:

@chris, do you have a patch? if not please don't criticize what is lacking. this project only thrives because of the volunteers who keep it going. no one is paid to maintain NH, or owes anyone anything.

you are welcome to supply a patch for the nuget issue, but don't just demand it be updated because you were inconvenienced.

--
You received this message because you are subscribed to the Google Groups "nhusers" group.

To view this discussion on the web visit https://groups.google.com/d/msg/nhusers/-/BYB9x7LjMtkJ.

To post to this group, send email to nhu...@googlegroups.com.
To unsubscribe from this group, send email to nhusers+u...@googlegroups.com.
For more options, visit this group at http://groups.google.com/group/nhusers?hl=en.

[Chris Bohling]

@Jason: I am neither a developer nor an administrator on the NHibernate Contrib project, true enough. I want to use NHibernate Validator as a third-party tool through NuGet, but it is looking like this will actually involve a great deal of effort. Either I will have to become intimately familiar with the code and the process of updating it for the community, or I will have to individually manage the problems that arise when no one tests a Contrib project (at least Validator) against the current release of NHibernate.

Here is my workaround (in NHibernate.Validator.Util.NHibernateHelper):

(add) using System;

...

(modify line 76, now 77)  catch (Exception) //ProxyFactoryFactoryNotConfiguredException

It seems to me that an active developer on the project could make this "patch" pretty quickly, if it is an acceptable alternative.

The real problem is that the single version of NHibernate Validator available on NuGet is incompatible with the single version of NHibernate available on NuGet. You might think that this is okay; I don't.