Resteasy hibernatevalidator provider not picked up as jboss module

[andrei.serea]

Hello everyone!

I have been trying for the past 2 days to create a basic setup with jax-rs and the validation api.

I used Jbos AS 7.1.1, resteasy jaxrs, and hibernate validator.

Adding the hibernate validator provider to my war's lib directory solves this problem easily.

But what I wanted to do and I seem to have a problem accomplishing is loading the resteasy hibernate validator provider as a MODULE in Jboss AS.

Here's my module.xml file:

{code:xml}<module xmlns="urn:jboss:module:1.1" name="org.jboss.resteasy.resteasy-hibernatevalidator-provider">
    <resources>
        <resource-root path="resteasy-hibernatevalidator-provider-2.3.2.Final.jar"/>
    </resources>
          <dependencies>
        <module name="javax.api"/>
        <module name="javax.enterprise.api"/>
        <module name="javax.servlet.api"/>
        <module name="javax.ws.rs.api"/>
                    <module name="javax.validation.api"/>
                    <module name="org.jboss.resteasy.resteasy-jaxrs"/>
                    <module name="org.hibernate.validator"/>
          </dependencies>
</module>{code}

If I add a dependency to this module using MANIFEST.MF Dependencies entry, resteasy doesn't pickup the provider and the validation is not triggered (but I can see from the logs that the module is processed and added to my war as part of the deployment). Even more, I can do something like:

{code:java}Class<?> clazz = Class.forName("org.jboss.resteasy.plugins.validation.hibernate.HibernateValidatorContextResolver");{code}

and get the class inside my app.

If I add the dependency as a global module in standalone.xml, resteasy picks up the provider and validation is called.

Can someone explain why it doesn't work with the Dependencies entry?

Thanks,

Andrei

[ctomc]

Hi,

how extactly do you define dependency?

you are probably missing importing of services.

instead of manifest.mf add jboss-deployment-structure.xml and add dependancy there together with service="import"

--

tomaz

[andrei.serea]

Thanks for your answer Tomaz! I have defined the dependency in Manifest.MF like this:

Manifest-Version: 1.0

Dependencies: org.jboss.resteasy.resteasy-hibernatevalidator-provider

Class-Path:

And that's the name I put in the module.xml also.

Is there a difference between the way the dependencies specified in MANIFEST are loaded from the ones mentioned in jboss-deployment-structure.xml?

/Andrei

[nickarls]

Does your directory structure match the dot-notation of the module name (plus the main dir)?

[andrei.serea]

Yes. I guess I wouldn't be able to do a successful Class.forName otherwise, right? I mean the classes in the module are in the classpath of my app but somwhow resteasy doesn't pickup the provider unless the module is set as global.

[nickarls]

Hmm. My guess would be that the deployer scans the application, sees that it uses hibernate and adds the hibernate dependecy and the classloader goes from there. Tried filtering out hibernate in jboss-deployment-structure.xml and pull it in through your own module?

[matlach]

see resolved issue : https://issues.jboss.org/browse/AS7-5711