Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Not able to make it work as a WildFly 8.1.0 module #2

Closed
rparree opened this issue Jun 17, 2014 · 1 comment
Closed

Not able to make it work as a WildFly 8.1.0 module #2

rparree opened this issue Jun 17, 2014 · 1 comment

Comments

@rparree
Copy link

rparree commented Jun 17, 2014

Hi,

I have been trying to make it work in WildFly 8.1.0. My deployment is a jar file containing a couple of MDBs.

One issue i have is that i need to bundle my ejb-jar in an ear together with mybatis plus the cdi extension. I am not able to make it work with a module.

This is my module.xml

<module xmlns="urn:jboss:module:1.3" name="org.mybatis.mybatis">

    <resources>
        <resource-root path="mybatis-3.2.7.jar"/>
        <resource-root path="mybatis-cdi-1.0.0-beta1.jar"/>
    </resources>
    <dependencies>
        <module name="javax.enterprise.api"/>
        <module name="javax.api"/>
    <module name="org.javassist"/>  
    <module name="javax.transaction.api"/> 
    </dependencies> 
</module> 

and this is my deployment-structure.xml

<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
    <deployment>
        <dependencies>
            <module name="org.jboss.logmanager"/>
            <module name="org.slf4j"/>
            <module name="org.mybatis.mybatis"/>

        </dependencies>
    </deployment>
</jboss-deployment-structure>

Anybody more luck with this?

tx.,

@rparree rparree changed the title Not able to make it work a WildFly 8.1.0 module Not able to make it work as a WildFly 8.1.0 module Jun 17, 2014
@mnesarco
Copy link
Member

This is a very specific and not standard configuration. Also you did not provide enough information like exceptions or log messages to figure out what happens. I am closing this issue. If it is still critical and you can help with tests and additional info, please reopen.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants