can inability to write index file for jboss 7 module prevent startup

[gsinghal]

I have a jboss module with a configuration like following:

<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>

So the myexternalmodule.jar file resides somewhere outside of jboss installation directory and i did specify a relative path so it is able to find the file correctly. But it is also trying to create a .index file(myexternalmodule.jar.index) in the same external location, I cannot have write permissions to that directory though, would that prevent jboss from coming up? I don't see any error indicating that thats the reason JBoss is failing to come up but since i do see an index file for the first jar but not the external jar I was thinking it might be a reason.

[sfcoy]

That seems like a very fragile way of doing things.

Why not just copy myexternalmodule.jar into your module?

Incidentally, I'm not sure that relative paths are supported as resource-root entries in any event.

[jaikiran]

Like Steve, I too am not sure if jboss-modules allows you to point to resources which are relative to the location of the module definition file and that too outside of the "module home".

gaurav singhal wrote:

I don't see any error indicating that thats the reason JBoss is failing to come up

Please post the logs that you see and any exception stacktraces.

[ctomc]

Hi,

.index file is created only if there is none present yet, so you can just give him permision for first boot and after that no need to have write permisions in that directory.

--

tomaz