Specify absolute path to a jar file in module.xml

[gsinghal]

is there a way to specify an absolute path to the jar file in module.xml, something like below:

<module xmlns="urn:jboss:module:1.1" name="mymodule">

   <resources>

        <resource-root path="mymodule.jar"/>

        <resource-root path="/u/users/myid/myexternalmodule.jar"/>

    </resources>

</module>

I tried above but it simply appends the path to the directory that the "mymodule.jar" is in, so is there any way to put an absolute path to find a jar thats external to jboss installation?

[jaikiran]

Why do you want to keep that jar outside of the module?

[nickarls]

Never tried but the docs say that "The path of this resource root, relative to the location of the module.xml file". Perhaps some ".." trick might work but not sure if you can get to any path from there.

[gsinghal]

Its a jar file thats delivered by another product so we need to point to that using an absolute path.

[guinotphil]

Can't you just copy the jar file within your module or within your own Nexus repository.

I use different versions and other libraries as modules which as not included on the default AS-7 installation. To easily deploy them to any AS-7 installation, I customised JBoss' Ant files to retrieve the jar from Nexus and re-create the module directory. I think this is better than having your production dependent to an external directory.

[gaoyonglu]

I have one way,that use linux ls -s Soft connection

[gaoyonglu]

you can see https://community.jboss.org/message/799782#799782

if db2 driver update ,I want the jboss no need update module,so I need dependent to an external directory

[zhouyaguo]

jaikiran pai wrote:

Why do you want to keep that jar outside of the module?

There is a case as following:

In our production environment, we install db2 client on every machine. If db2 driver is installed as a module into jboss as 7 , i have to replace the jar when upgrading the db2 client instance, i don't like to do the upgrade in *2* steps.

I set the db2 client jar to classpath in jboss as 5 and it worked fine, but the situation is different in jboss modules in jboss as 7.