JBoss Remote Deployment

There used to be a way to deploy j2ee modules to remote JBoss instances via
HTTP/SSH/FTP. I cannot find this in #5706. Has it been dropped?

Sascha

4 comments

Sascha,

Due to the changes in Demetra the whole JBoss plugin has been completely rewritten from scratch. Especially the remote deployment part has to be implemented completely different, and it isn't finished yet. And as Demetra has entered stabilization phase, it won't make it into 6.0. But you may expect it for one of the first minor releases after 6.0.

- Martin

0

Thanks for the info, Martin. By the way: JBoss remote connection configurations
don't work at all at the moment (see the exception below, also auto-submitted).
And sorry if it's a dumb question, but what's a remote connection good for
anyway if there's no remote deployment method available?

Sascha

java.lang.NoClassDefFoundError: org/jnp/interfaces/NamingContextFactory
at com.fuhrer.idea.jboss.server.JBossServer.getInitialContext(JBossServer.java:128)
at com.fuhrer.idea.jboss.server.JBossServer.getServer(JBossServer.java:105)
at com.fuhrer.idea.jboss.server.JBossServer.isConnected(JBossServer.java:59)
at
com.fuhrer.idea.javaee.server.JavaeeServerInstance.isConnected(JavaeeServerInstance.java:145)
at
com.fuhrer.idea.javaee.server.JavaeeServerInstance.connect(JavaeeServerInstance.java:64)
at
com.intellij.javaee.run.execution.J2EERemoteState.execute(J2EERemoteState.java:1)

Martin Fuhrer wrote:

Sascha,

Due to the changes in Demetra the whole JBoss plugin has been completely rewritten from scratch. Especially the remote deployment part has to be implemented completely different, and it isn't finished yet. And as Demetra has entered stabilization phase, it won't make it into 6.0. But you may expect it for one of the first minor releases after 6.0.

- Martin

0

The NamingContextFactory class is read from ]]>/client/jbossall-client.jar. Could you please check if this file is there, readable, etc.?

And why use remote connections on the local machine?
Well, there are different reasons. You can switch projects without having to permanently start/stop the server, you can have two different projects using the same server simultaneously, you can run the server as a different user, etc. Personally I don't use remote connections that often, especially not when debugging.

Please be aware that the plugin is a development tool, not a deployment tool. You can't use it to do productive deployment, as it doesn't deploy permanently. As soon as the server is restarted for whatever reason, the applications deployed through the plugin are not available anymore.

0

Martin Fuhrer wrote:

The NamingContextFactory class is read from <JBOSS_HOME>/client/jbossall-client.jar. Could you please check if this file is there, readable, etc.?


Yes, it's there, but the application server config got broken with the switch to
the bundled JBoss plugin: The configured libraries were still there, but the
JBoss home-directory configuration was gone.

In any case, it shouldn't crash like this in case the libraries are not there.

Please be aware that the plugin is a development tool, not a deployment tool. You can't use it to do productive deployment, as it doesn't deploy permanently. As soon as the server is restarted for whatever reason, the applications deployed through the plugin are not available anymore.


I am fully aware of that, but I was hoping to get some help from the plugin to
make the best use of the resources I have available: A development machine and a
server machine I can and develop with and deploy to. This is what I thought a
"Remote Connection" is basically good for - I guess i misunderstood that term.
I'll patiently wait for the minor release then ;)

Sascha

0

Please sign in to leave a comment.