I've implemented some code using javax.validation and Hibernate Validator. The unit tests are working fine. The build produces OSGi bundles and features, and runs in Karaf.
"Unable to create a Configuration, because no Bean Validation provider could be found. Add a provider like Hibernate Validator (RI) to your classpath."
I would include the stacktrace, but it doesn't look useful to me. Most of it is in my code, junit, and paxexam.
I'm attempting to use version 5.4.1.Final of HV. Note again that the unit tests doing validation are working fine. It took a while to get the dependencies correct to get that far (like using version "3.0.1-b08" of "javax.el".
I've seen some mentions of a "hibernate-validator-osgi-karaf-features" artifact, but I'm not sure if that's relevant. I'm attempting to use both the hibernate-validator artifact and the hibernate-validator-annotation-processor artifact.
Thanks for the reply, but I need more information. I might be able to get the integration test you refer to working, but I have to integrate the required references into my pom and features files.
But I guess that shouldn't be that surprising, as that artifact is a POM artifact, not a JAR artifact. Is there some way to reference a POM artifact in a features.xml file?
The "hibernate-validator-osgi-karaf-features" artifact is just an example features file which we use to run integration tests.
I've made progress in correctly referencing features, but I'm effectively back to the original problem. I finally figured out that I need to just reference the "hibernate-validator" feature from the "hibernate-validator-osgi-karaf-features" artifact, but the result is the same. It stills says it can't find HV in the classpath.
I tried changing the "LogLevel" in my PaxExam configuration from WARNING to DEBUG. This gives me a lot more information, but perhaps not very useful. Is there some way I could set debug levels that might help explain why it can't find HV in the classpath?