I've run into the remote deploy problem, too. It looks to me like you simply CAN'T perform remote deployment with JBoss-IDE. If you use the MainDeployer JMX mbean (i.e. you set up an http:// URL pointing to your remote JBoss server) it still won't work.
The MainDeployer takes a java.net.URL argument, and JBoss-IDE appends a file URL (i.e. the file URL for your deployment archive) as the argument. If you've specified a remote server instead of localhost, the remote JBoss will look for the file URL on its filesystem, not on the filesystem of your development box. If JBoss-IDE let you specify the URL to use for the argument that is passed to MainDeployer, you could get around this by making the deployment archive available via ftp or http on your local machine. Then, the remote JBoss server would grab the file from your local development box. Unfortunately, JBoss-IDE doesn't let you specify the argument, but appends it automatically. I'm no expert, so if I'm mistaken about this, someone please correct me, but that's the way it looks to me. <a href="http://www.jboss.org/index.html?module=bb&op=viewtopic&p=3824573#3824573";>View the original post</a> <a href="http://www.jboss.org/index.html?module=bb&op=posting&mode=reply&p=3824573>Reply to the post</a> ------------------------------------------------------- This SF.Net email is sponsored by: IBM Linux Tutorials Free Linux tutorial presented by Daniel Robbins, President and CEO of GenToo technologies. Learn everything from fundamentals to system administration.http://ads.osdn.com/?ad_id=1470&alloc_id=3638&op=click _______________________________________________ JBoss-Development mailing list [EMAIL PROTECTED] https://lists.sourceforge.net/lists/listinfo/jboss-development
