Seam 2.0 is tightly coupled with Hibernate validator

[thejavafreak]

No offence, I think Hibernate validator is one great product. But does it need to be tightly integrated with Seam 2.0? Since in org.jboss.seam.core.validators, it's @Install(precedence=BUILT_IN)

The issue is if user chooses not to use Hibernate as the persistence strategy or Hibernate validator also if that library is not bundled in the appserver such as glassfish.

I know it's just a matter of adding hibernate-validator.jar in the classpath. But again if user doesn't use it, won't it just be useless? Will it be better if the precedence is not BUILT_IN? Or are there other thoughts regarding this?

Just my two cents

[gavin.king]

Hibernate Validator now works with any JPA provider, check the docs.

[thejavafreak]

The issue is not that. The issue is whether I want to use it or not. If I don't use hibernate-validator at all, that means I'm wasting one library that never will be used at all in my apps.

[gavin.king]

I checked the code - there are actually four hard dependencies to Hibernate Validator:

FacesMessages
Param
Validators
BaseSeamTest

I guess it would be *possible* to get rid of the hard dependency, but it wouldn't be simple.

[thejavafreak]

Thanks gavin. I think it would be best for users just to instantiate hibernate-validator component via components.xml