Distributed deploy classpath?

[jaaron]

Is it possible to set up a 'distributed' deploy classpath? What I mean by that is is it possible to deploy my jar files on a seperate server than the one JBoss is installed on and then just include some pointer to that directory in my configuration files? Can I have more than one instance of JBoss pointing to that central deploy directory?

I apologize if this question has already been addressed on the forum and/or manuals, but I've spent several days now and haven't found anything. I'm familiar with the auto deployment properties in the jboss.jcml file, but I can't seem to get JBoss to recognize anything but local directories.

If it helps at all, I'm running all this with JBoss 2.4.4 and in a WindowsNT/2000 environment.

Thanks,
jaaron

[adrian.brock]

Sorry, it is not possible use the AutoDeployer on a
remote directory(url), it uses java.io.File, you
can only do it on single deployment urls.

Put it on the feature requests on sourceforge.

I think this can be done using ldap? I believe Tomcat
does it this way when running standalone?

Regards,
Adrian

[jaaron]

Well, this is interesting. After working with it some more, I was able to get the following to work:

My Auto-Deploy class path was set as follows:

../deploy,../deploy/lib,//xxx.xxx.xxx.131/deploy

The computer at xxx.xxx.xxx.131 is running NT 4.0 and has a directory named "deploy" set to allow any user to share access. In that deploy folder is a message driven bean jar file.

When JBoss starts up, it says that is DOES load the bean. Not only that, if I run an application to send JMS messages to that bean, they make it through. And even if, after starting JBoss, I turn off the computer hosting the remote bean, the application still seems to work! Now this is exactly what I was hoping for, but from what I understand it's not suppose to work that way. Or am I wrong? Or should I not expect reliable results when remotely deploying a bean like this?

Does anyone else have any experiences like this?

Thanks,
jaaron

[adrian.brock]

Interesting.

This must be a shared folder, e.g.

dir \\othermachine\sharename

I'll have to try this myself when I've got a bit more time.
See what protocol java thinks it is using.

Regards,
Adrian

[jaaron]

It is a shared folder, with no restrictions on access.

If anyone has any insights on this, I'd appriciate them.

Thanks,
jaaron