Hi,

I am playing with the validation part of hibernate annotations and it is very well designed.
I am not interested by the metadata part but I just want to use the validator. My problem is that the validator part is hibernate dependent.
I don't understand why. With this dependency, I must put hibernate jar on the client side and I don't want to do so.

It would be great to split the annotation jar in two parts, one for metadata support and one for the validator framework. This second jar could be made hibernate independent. Thus I could deploy it on the client. More generelly this could open the validator framework to everybody (not only hibernate users)

Does this make sense for you ? Is there anybody else that has the same requirement

Regards

Seb

Some other people have resquested such a thing, but I'm busy on other priorities. If someone provide a patch, I'll consider it.

I went a little bit deeper in the code and it seems to be a difficult task to achieve.

I managed to get only one dependency between validator and hibernate but I can't imagine how to avoid it. In ClassValidator.geInvalidValues, the framework check if a property is initialized before checking validation rules. To do so, it calls the Hibernate.isPropertyInitialized method.

This seems to be a mandatory check on the server to avoid unnecessary initializations during the validation process. So I don't know how to get rid of this dependency

Seb

just a quick thought, without kowing the validiator ...

Why not let the user of the validation-fw pass in that dependency? Provide an interface and a default-implementation to do that check (e.g. default always returns 'true').

If someone wants 'Hibernate.isPropertyInitialized' he must provide an own implementation of your interface (e.g. during initialization of the Validator).

Then you don't have that dependency to hibernate and it would be an easy task to provide an own implementation of your interface.

Or design it as a callback or something like this.

gtx
curio