I'm trying to simplify the provisioning of JBoss EAP 6 applications by adding common components to the base EAP 6 installation directory (e.g. ojdbc driver).
For the WMQ JCA resource adapter, I have everything working just fine if I put the 'wmq.jmsra.rar' archive in the 'deployments' folder. I just need to configure the resource-adapters section of the standalone.xml file according to the official documentation.
Now, is it possible to create a JBoss module and include it via the 'global-modules' section? I tried creating a module wmq.ra with resource-root wmq.jmsra.rar, but the module won't load.
I may have found the answer i was looking for. I ran into post about the similar issue for Active MQ here and here. I followed the same canvas for WMQ:
unpack the wmq.jmsra.rar in your module directory (e.g. modules/wmq/jmsra/main/)
create a module.xml descriptor for you module
this one worked for me with WMQ 7.5.0.3. I had problems when some of the dependencies were missing
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="wmq.jmsra">
<resources>
<resource-root path="."/>
<resource-root path="com.ibm.mq.commonservices.jar"/>
<resource-root path="com.ibm.mq.connector.jar"/>
<resource-root path="com.ibm.mq.headers.jar"/>
<resource-root path="com.ibm.mq.jar"/>
<resource-root path="com.ibm.mq.jmqi.jar"/>
<resource-root path="com.ibm.mq.jmqi.local.jar"/>
<resource-root path="com.ibm.mq.jmqi.remote.jar"/>
<resource-root path="com.ibm.mq.jmqi.system.jar"/>
<resource-root path="com.ibm.mq.jms.admin.jar"/>
<resource-root path="com.ibm.mq.pcf.jar"/>
<resource-root path="com.ibm.mqjms.jar"/>
<resource-root path="com.ibm.msg.client.commonservices.j2se.jar"/>
<resource-root path="com.ibm.msg.client.commonservices.jar"/>
<resource-root path="com.ibm.msg.client.jms.internal.jar"/>
<resource-root path="com.ibm.msg.client.jms.jar"/>
<resource-root path="com.ibm.msg.client.matchspace.jar"/>
<resource-root path="com.ibm.msg.client.provider.jar"/>
<resource-root path="com.ibm.msg.client.ref.jar"/>
<resource-root path="com.ibm.msg.client.wmq.common.jar"/>
<resource-root path="com.ibm.msg.client.wmq.factories.jar"/>
<resource-root path="com.ibm.msg.client.wmq.jar"/>
<resource-root path="com.ibm.msg.client.wmq.v6.jar"/>
<resource-root path="dhbcore.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.resource.api"/>
<module name="javax.jms.api"/>
<module name="javax.management.j2ee.api"/>
</dependencies>
</module>
import your module the usual way in standalone.xml
I didn't fully validate this solution in production like environment, I'll update if needed.
You can refer to EAP6 and WebSphere MQ Integration document for installing and configuring the resource adapter.
Related
This question is a spinoff of this one!
I now can configure my project to use a different version of Hibernate and my JBoss installation has a second slot named "5.1.1.Final" (located at ...\jboss-as-7.1.3.Final\modules\org\hibernate\5.1.10.Final) that has the following module.xml file:
<module xmlns="urn:jboss:module:1.1" name="org.hibernate:5.1.10.Final">
<resources>
<resource-root path="hibernate-core-5.1.10.Final.jar"/>
<resource-root path="hibernate-entitymanager-5.1.10.Final.jar"/>
<resource-root path="hibernate-infinispan-5.1.10.Final.jar"/>
<!-- Insert resources here -->
</resources>
<dependencies>
<module name="asm.asm"/>
<module name="javax.api"/>
<module name="javax.persistence.api"/>
<module name="javax.transaction.api"/>
<module name="javax.validation.api"/>
<module name="org.antlr"/>
<module name="org.apache.commons.collections"/>
<module name="org.dom4j"/>
<module name="org.infinispan" optional="true"/>
<module name="org.javassist"/>
<module name="org.jboss.as.jpa.hibernate" slot="4" optional="true"/>
<module name="org.jboss.logging"/>
<module name="org.hibernate.envers" services="import" optional="true"/>
<module name="org.hibernate.commons-annotations"/>
</dependencies>
</module>
However, when JBoss starts I receive the following error message: ParseError at [row,col]:[26,72] Message: Invalid/mismatched module name (expected org.hibernate:5.1.10.Final).
I can't understand why this message, since the required module name (org.hibernate:5.1.10.Final) is the exact name I specified at the file (name="org.hibernate:5.1.10.Final");
What am i missing?
The slot is a separate attribute. It should look like the following.
<module xmlns="urn:jboss:module:1.1" name="org.hibernate" slot="5.1.10.Final">
On a side note you may want to consider trying to upgrade to WildFly 11, current release is WildFly 11.0.0.Beta1. I'm not sure if Hibernate 5.1.x will work with JBoss AS 7.x. WildFly 10.1.0.Final uses Hibernate 5.0.10.Final.
I am creating global module in wildfly which includes xml-api jar as well.
But When the parsing happens for the xml file, it throws the following exception.
I searched in the forum and many post saying to remove the xml-api and xml-beans jars from the class path. Because there is a conflict of JBoss / JDK xml jars and our xml-api jars. But I need to have my jars to be loaded with precedence. How can I achieve that. Please provide the suggestion.
13:11:51,686 ERROR [stderr] (default task-1) Caused by: java.lang.ClassCastExcep
tion: __redirected.__DatatypeFactory cannot be cast to javax.xml.datatype.Dataty
peFactory
13:11:51,688 ERROR [stderr] (default task-1) at javax.xml.datatype.DatatypeFa
ctory.newInstance(Unknown Source)
13:11:51,690 ERROR [stderr] (default task-1) at com.thoughtworks.xstream.conv
erters.extended.DurationConverter$1.getFactory(DurationConverter.java:39)
13:11:51,691 ERROR [stderr] (default task-1) at com.thoughtworks.xstream.conv
erters.extended.DurationConverter.<init>(DurationConverter.java:44)
13:11:51,691 ERROR [stderr] (default task-1) ... 74 more
Thanks
Senthil
I solved the issue.
I have removed the below modules and added javax.api and org.slf4j as dependencies in my module.xml. It is because wildfly already having these modules and loaded as part of core class loading. Thats why there is a conflict when it is reloaded.
Module.xml
Removed content :
<resource-root path="xml-apis-<version>.jar">
<resource-root path="slf4j-api-<version>.jar"/>
Added content :
<dependencies>
<module name="javax.api"/>
<module name="org.slf4j"/>
</dependencies>
corrected Module.xml
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.3" name="drools">
<resources>
<resource-root path="aether-api-1.0.0.v20140518.jar"/>
<resource-root path="aether-connector-basic-1.0.0.v20140518.jar"/>
<resource-root path="aether-impl-1.0.0.v20140518.jar"/>
<resource-root path="aether-spi-1.0.0.v20140518.jar"/>
<resource-root path="aether-transport-file-1.0.0.v20140518.jar"/>
<resource-root path="aether-transport-http-1.0.0.v20140518.jar"/>
<resource-root path="aether-transport-wagon-1.0.0.v20140518.jar"/>
<resource-root path="aether-util-1.0.0.v20140518.jar"/>
<resource-root path="ant-1.8.3.jar"/>
<resource-root path="ant-launcher-1.8.3.jar" />
<resource-root path="antlr-runtime-3.5.jar"/>
<resource-root path="aopalliance-1.0.jar"/>
<resource-root path="cdi-api-1.0-SP4.jar"/>
<resource-root path="commons-codec-1.4.jar"/>
<resource-root path="commons-lang-2.6.jar"/>
<resource-root path="commons-logging-1.1.1.jar"/>
<resource-root path="dom4j-1.6.1.jar"/>
<resource-root path="drools-beliefs-6.5.0.Final.jar"/>
<resource-root path="drools-compiler-6.5.0.Final.jar"/>
<resource-root path="drools-core-6.5.0.Final.jar"/>
<resource-root path="drools-decisiontables-6.5.0.Final.jar"/>
<resource-root path="drools-jsr94-6.5.0.Final.jar"/>
<resource-root path="drools-persistence-jpa-6.5.0.Final.jar"/>
<resource-root path="drools-pmml-6.5.0.Final.jar"/>
<resource-root path="drools-reteoo-6.5.0.Final.jar"/>
<resource-root path="drools-scorecards-6.5.0.Final.jar"/>
<resource-root path="drools-verifier-6.5.0.Final.jar"/>
<resource-root path="drools-templates-6.5.0.Final.jar"/>
<resource-root path="ecj-4.4.2.jar"/>
<resource-root path="guava-13.0.1.jar"/>
<resource-root path="hibernate-jpa-2.0-api-1.0.1.Final.jar"/>
<resource-root path="httpclient-4.3.6.jar"/>
<resource-root path="httpcore-4.3.3.jar"/>
<resource-root path="itext-2.1.2.jar"/>
<resource-root path="javassist-3.18.1-GA.jar"/>
<resource-root path="javax.inject-1.jar"/>
<resource-root path="jaxb-core-2.2.11.jar"/>
<resource-root path="jaxb-impl-2.2.11.jar"/>
<resource-root path="jboss-interceptors-api_1.1_spec-1.0.1.Final.jar"/>
<resource-root path="jboss-transaction-api_1.1_spec-1.0.1.Final.jar"/>
<resource-root path="jcl-over-slf4j-1.7.2.jar"/>
<resource-root path="jsoup-1.8.3.jar"/>
<resource-root path="jsr94-1.1.jar"/>
<resource-root path="jsr250-api-1.0.jar"/>
<resource-root path="kie-api-6.5.0.Final.jar"/>
<resource-root path="kie-ci-6.5.0.Final.jar"/>
<resource-root path="kie-internal-6.5.0.Final.jar"/>
<resource-root path="knowledge-api-6.5.0.Final.jar"/>
<resource-root path="maven-aether-provider-3.2.5.jar"/>
<resource-root path="maven-artifact-3.2.5.jar" />
<resource-root path="maven-compat-3.2.5.jar"/>
<resource-root path="maven-core-3.2.5.jar"/>
<resource-root path="maven-model-3.2.5.jar"/>
<resource-root path="maven-model-builder-3.2.5.jar"/>
<resource-root path="maven-plugin-api-3.2.5.jar"/>
<resource-root path="maven-repository-metadata-3.2.5.jar"/>
<resource-root path="maven-settings-3.2.5.jar"/>
<resource-root path="maven-settings-builder-3.2.5.jar"/>
<resource-root path="mvel2-2.2.8.Final.jar"/>
<resource-root path="org.eclipse.sisu.inject-0.3.0.M1.jar"/>
<resource-root path="org.eclipse.sisu.plexus-0.3.0.M1.jar"/>
<resource-root path="plexus-cipher-1.7.jar"/>
<resource-root path="plexus-classworlds-2.5.2.jar"/>
<resource-root path="plexus-component-annotations-1.5.5.jar"/>
<resource-root path="plexus-interpolation-1.21.jar"/>
<resource-root path="plexus-sec-dispatcher-1.3.jar"/>
<resource-root path="plexus-utils-3.0.20.jar"/>
<resource-root path="poi-3.13.jar"/>
<resource-root path="poi-ooxml-3.13.jar"/>
<resource-root path="poi-ooxml-schemas-3.13.jar"/>
<resource-root path="protobuf-java-2.6.0.jar"/>
<resource-root path="sisu-guice-3.2.3-no_aop.jar"/>
<!-- <resource-root path="slf4j-api-1.7.2.jar"/> -->
<resource-root path="stax-api-1.0.1.jar"/>
<resource-root path="wagon-http-2.6.jar"/>
<resource-root path="wagon-http-shared-2.6.jar"/>
<resource-root path="wagon-provider-api-2.6.jar"/>
<resource-root path="xmlbeans-2.3.0.jar"/>
<resource-root path="xmlpull-1.1.3.1.jar"/>
<resource-root path="xpp3_min-1.1.4c.jar"/>
<resource-root path="xstream-1.4.9.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="org.slf4j"/>
</dependencies>
</module>
Thanks
Senthil
I am currently migrating apps from JBoss 5.1 to JBoss 7.0 EAP server.
I have added a module to JBoss server named - org.springframework for spring dependency jars
<?xml version="1.0" ?>
<module xmlns="urn:jboss:module:1.1" name="org.springframework">
<resources>
<resource-root path="spring-core-3.0.5.RELEASE.jar"/>
<resource-root path="spring-context-3.0.5.RELEASE.jar"/>
<resource-root path="spring-beans-3.0.5.RELEASE.jar"/>
<resource-root path="spring-expression-3.0.5.RELEASE.jar"/>
<resource-root path="spring-web-3.0.5.RELEASE.jar"/>
<resource-root path="spring-aop-3.0.5.RELEASE.jar"/>
<resource-root path="spring-asm-3.0.5.RELEASE.jar"/>
<resource-root path="spring-jdbc-3.0.5.RELEASE.jar"/>
<resource-root path="spring-tx-3.0.5.RELEASE.jar"/>
<resource-root path="org.springframework.web.servlet-3.0.0.M3.jar"/>
<resource-root path="commons-logging-1.1.1.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="javax.servlet.jsp.api"/>
<module name="javax.faces.api"/>
</dependencies>
</module>
I have defined the module dependency in jboss-deployment-structure.xml of the WAR
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="com.oracle" />
<module name="org.springframework" />
</dependencies>
</deployment>
</jboss-deployment-structure>
The war deployed to server also contains spring-context-3.0.5.RELEASE.jar in its WEB-INF/lib folder
So I think the required jar - spring-context-3.0.5.RELEASE.jar exists in class path. But still I am getting the below error :
04:33:30,496 INFO [org.springframework.beans.factory.xml.XmlBeanDefinitionReader] (default task-19) Loading XML bean definitions from class path resource [core_services.xml]
04:33:30,507 INFO [org.springframework.beans.factory.support.DefaultListableBeanFactory] (default task-19) Pre-instantiating singletons in org.springframework.beans.fact
ory.support.DefaultListableBeanFactory#9b765aa: defining beans [LogService,CacheService,PropertyService]; root of factory hierarchy
2017.02.09 04:33:30 ERROR CashViewsPortalServiceImpl(-2): org/springframework/context/support/ClassPathXmlApplicationContext
CallStack=java.lang.NoClassDefFoundError: org/springframework/context/support/ClassPathXmlApplicationContext
at com.karthik.common.service.Services.getService(Services.java:31)
at com.karthik.data.service.DataServices.getService(DataServices.java:18)
at com.karthik.portal.server.PortalServiceImpl.getInitializeInfo(PortalServiceImpl.java:83)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:497)
at com.google.gwt.user.server.rpc.RPC.invokeAndEncodeResponse(RPC.java:561)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processCall(RemoteServiceServlet.java:265)
at com.google.gwt.user.server.rpc.RemoteServiceServlet.processPost(RemoteServiceServlet.java:305)
at com.google.gwt.user.server.rpc.AbstractRemoteServiceServlet.doPost(AbstractRemoteServiceServlet.java:62)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:790)
at io.undertow.servlet.handlers.ServletHandler.handleRequest(ServletHandler.java:85)
at io.undertow.servlet.handlers.security.ServletSecurityRoleHandler.handleRequest(ServletSecurityRoleHandler.java:62)
at io.undertow.servlet.handlers.ServletDispatchingHandler.handleRequest(ServletDispatchingHandler.java:36)
at org.wildfly.extension.undertow.security.SecurityContextAssociationHandler.handleRequest(SecurityContextAssociationHandler.java:78)
at io.undertow.server.handlers.PredicateHandler.handleRequest(PredicateHandler.java:43)
at io.undertow.servlet.handlers.security.SSLInformationAssociationHandler.handleRequest(SSLInformationAssociationHandler.java:131)
at io.undertow.servlet.handlers.security.ServletAuthenticationCallHandler.handleRequest(ServletAuthenticationCallHandler.java:57)
1) Why do we need add module in Jboss 7 EAP server for class loading even though the jars are bundled in WEB-INF/lib folder of the war
deployed on server?
2) How to resolve the above error?
I think you have n't defined the spring dependencies perfectly. Below are the steps:
You can define Spring as a module
The following are steps to create a Spring module:
1.Download the desired version of Spring. For this example we are using Spring 3.1.1.
2.Create the directory: $JBOSS_HOME/modules/org/springframework/spring/main.
3.Copy the Spring libraries you downloaded to that directory.
4.Create module.xml with the following contents under that directory. Make sure these correspond to the libraries' names:
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.1" name="org.springframework.spring">
<resources>
<resource-root path="org.springframework.aop-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.asm-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.aspects-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.beans-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.context-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.context.support-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.core-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.expression-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.instrument-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.instrument.tomcat-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.jdbc-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.jms-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.orm-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.oxm-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.test-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.transaction-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.web-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.web.portlet-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.web.servlet-3.1.1.RELEASE.jar"/>
<resource-root path="org.springframework.web.struts-3.1.1.RELEASE.jar"/>
</resources>
<dependencies>
<module name="org.apache.commons.logging"/>
<module name="javax.api" export="true"/>
<module name="org.jboss.vfs"/>
</dependencies>
</module>
Here is an absolute minimal module.xml (the different Spring version is irrelevant):
<?xml version="1.0"?>
<module xmlns="urn:jboss:module:1.1" name="org.springframework.spring">
<resources>
<resource-root path="spring-aop-3.2.3.RELEASE.jar"/>
<resource-root path="spring-beans-3.2.3.RELEASE.jar"/>
<resource-root path="spring-context-3.2.3.RELEASE.jar"/>
<resource-root path="spring-core-3.2.3.RELEASE.jar"/>
<resource-root path="spring-expression-3.2.3.RELEASE.jar"/>
</resources>
<dependencies>
<module name="javax.api"/>
<module name="org.apache.commons.logging"/>
</dependencies>
</module>
5.Put the following jboss-deployment-structure.xml in your application archive (WEB-INF/jboss-deployment-structure.xml for WAR or META-INF/jboss-deployment-structure.xml for EAR or EJB-jar) to use the above module:
If you're using JBoss EAP 6.1.x and greater or EAP 7, then use below:
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.springframework.spring" export="true" meta-inf="export"/>
</dependencies>
</deployment>
</jboss-deployment-structure>
If JBoss EAP 6.0.x, then use below
<?xml version="1.0" encoding="UTF-8"?>
<jboss-deployment-structure>
<deployment>
<dependencies>
<module name="org.springframework.spring" export="true">
<imports>
<include path="META-INF**"/>
<include path="org**"/>
</imports>
<exports>
<include path="META-INF**"/>
<include path="org**"/>
</exports>
</module>
</dependencies>
</deployment>
</jboss-deployment-structure>
Note: The meta-inf on the module in the jboss-deployment-structure.xml was added in JBoss EAP 6.1.0, which allows the files in the META-INF of a resource to be visible. Since this was not available in JBoss EAP 6.0.x, the section allows you to get access to the META-INF directory which is not visible by default.
Note: The Spring Framework module should not include resources such as servlet-api.jar, xml-apis.jar, jta-api.jar, and other APIs. These APIs are implemented by either the JDK or JBoss and trying to use a different version of the API will lead to classloading issues and other problems.
Note: The Spring module should include all of its non Java / JavaEE dependencies. The Spring module can depend on javax.api / javaee.api provided by JBoss and any public JBoss module, but for other dependencies Spring has such as aopalliance, they would need to be included as resources in the module or in another custom module.
I want to define a module with a resource-root like this:
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.mymodule">
<resources>
<resource-root path="libs"/>
</resources>
<dependencies />
</module>
The directory contains all the libraries I need.
I've tried it and it not work, but if I put it this way it work:
<?xml version="1.0" encoding="UTF-8"?>
<module xmlns="urn:jboss:module:1.0" name="com.mymodule">
<resources>
<resource-root path="libs/lib1.jar"/>
<resource-root path="libs/lib2.jar"/>
<resource-root path="libs/lib3.jar"/>
<resource-root path="libs/lib4.jar"/>
........
</resources>
<dependencies />
</module>
Is there a way to do it the first?
Try and use libs.* in your first implementation
UPDATE:
This feature is not currently available, though its under R&D
If you need to include multiple jars in a module, you will need to instantiate each indivisually
I know this one is old, but I just had the same problem on EAP-7 and solved it as follows:
You may want to create the module using the JBoss CLI. My problem was to supply multiple resources as it was yours. I am using the attribute resource-delimiter and provide my list of resources as follows:
module add --name=my.module --resource-delimiter=, --resources=libA.jar,libB.jar,libC.jar --dependencies=my.dep.a,my.dep.b
This generates the following module.xml in the respective JBoss folder:
<?xml version="1.0" ?>
<module xmlns="urn:jboss:module:1.1" name="my.module">
<resources>
<resource-root path="libA.jar"/>
<resource-root path="libB.jar"/>
<resource-root path="libC.jar"/>
</resources>
<dependencies>
<module name="my.dep.a"/>
<module name="my.dep.b"/>
</dependencies>
</module>
Hope it helps.
I configured everything like they say here.
And it still won't run. It just gives me an LogManager exception.
Does anyone successfully run AspectJ there?
Here is a possible workaround/solution (from http://wiki.eclipse.org/LTWJboss7):
The IllegalStateException is thrown by jBoss7 because there is a bug
that limits access to java.util.logging:
https://issues.jboss.org/browse/AS7-1 - There a partial solution to
avoid this problem is suggested, regarding changing the way the
loadmanager is loaded, pushing it to the BootClasspath and adding
several configuration options. However we suggest deactivating the
AspectJ tracing facilities. You can achieve this by adding the next
options:
-Dorg.aspectj.tracing.enabled=false -Dorg.aspectj.tracing.factory=default
Due to new JBoss classloader and modularization architecture, classes
stored in your javaagent are not visible to the remaining modules, so
your aspects will not be found and you will get different types of
errors. To let your aspects been found by all your code you have to
add the aspectjweaver, and aspects.jar files to the bootclasspath and
add the next option to JBoss startup:
-Djboss.modules.system.pkgs=org.aspectj,com.yourcompany.aspects.package
that makes every class under those packages shared across all the
modules in the JBoss system.
This worked excellently for me ;).
I have configured three modules ec.com.acme, org.springframework, org.aspectj.
The key is to add the ironjacamar module as dependency of org.aspectj module and export them to be visible to all modules that depend on org.aspectj module, for example org.springframework module, as well:
org.aspectj Module Configuration:
<module xmlns="urn:jboss:module:1.1" name="org.aspectj">
<resources>
<resource-root path="aspectjweaver-1.7.2.jar"/>
</resources>
<dependencies>
<!--Add and export it to work-->
<module name="org.jboss.ironjacamar.jdbcadapters" export="true"/>
</dependencies>
</module>
Module Configuration org.springframework:
<module xmlns="urn:jboss:module:1.1" name="org.springframework">
<resources>
<resource-root path="com.springsource.org.aopalliance-1.0.0.jar"/>
<resource-root path="org.springframework.aop-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.asm-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.aspects-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.beans-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.context-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.context.support-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.core-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.expression-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.jdbc-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.orm-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.oxm-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.transaction-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.web-3.1.0.RELEASE.jar"/>
<resource-root path="org.springframework.web.servlet-3.1.0.RELEASE.jar"/>
<resource-root path="spring-batch-core-2.1.9.RELEASE.jar"/>
<resource-root path="spring-batch-infrastructure-2.1.9.RELEASE.jar"/>
</resources>
<dependencies>
<module name="org.apache.commons.logging" export="true"/>
<module name="org.hibernate" slot="3" export="true"/>
<module name="javax.api"/>
<module name="javax.annotation.api"/>
<module name="javax.el.api"/>
<module name="javax.enterprise.api"/>
<module name="javax.ejb.api"/>
<module name="javax.faces.api"/>
<module name="javax.interceptor.api"/>
<module name="javax.servlet.api"/>
<module name="javax.servlet.jsp.api"/>
<module name="javax.transaction.api"/>
<module name="javax.xml.bind.api"/>
<!--Add and export it to work-->
<module name="org.aspectj" export="true"/>
<module name="com.ibm.as400" slot="main" export="true"/>
</dependencies>
</module>
ec.com.acme Module Configuration:
<module xmlns="urn:jboss:module:1.1" name="ec.com.acme">
<resources>
<resource-root path="prjAcme.jar"/>
</resources>
<dependencies>
<module name="org.apache.commons.lang" slot="main" export="true"/>
<module name="org.apache.commons.beanutils" slot="main" export="true"/>
<module name="org.apache.commons.collections" slot="main" export="true"/>
<module name="org.apache.commons.io" slot="main" export="true"/>
<module name="org.apache.commons.lang3" slot="main" export="true"/>
<!--Add and export it to work-->
<module name="org.springframework" slot="main" export="true"/>
</dependencies>
</module>