Yes, the jboss plugin fully supports remote deployments and was really the reason I wrote it ;-)
Yes, IIRC you can only deploy valid supported types. .ejb is not a valid deployable. Jboss wants to see a war/jar/sar, etc. Please also keep in mind that remote deploying on JBoss means the deployment does not stick after a server reboot. Its just good to use for development. Jeff Kris Bravo wrote: > Does the jboss maven plugin support remote deployments? I assumed from > the docs that the following: > > <plugin> > <groupId>org.codehaus.mojo</groupId> > <artifactId>jboss-maven-plugin</artifactId> > <configuration> > <hostName>remote.server.domain</hostName> > <port>1115</port> > </configuration> > </plugin> > would transmit an ejb or ear file to the server and deploy it; however, > I'm getting the following error: > > Caused by: java.io.IOException: Server returned HTTP response code: 500 > for URL: > http://server.atlanta.ga.us:1115/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=deploy&argType=java.net.URL&arg0=file:/path-to-file/target/app-ejb-1.0.ejb > at > sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLConnection.java:1149) > at > org.codehaus.mojo.jboss.AbstractDeployerMojo.doURL(AbstractDeployerMojo.java:96) > > throwing this url in a browser returns this error: > Cause: org.jboss.deployment.DeploymentException: url > file:/path-to-file/target/app-ejb-1.0.ejb could not be opened, does it > exist? > > Is it a mistake that the file ends with .ejb instead of ear? > > If this isn't supported, please let me know. I've read somewhere that so > long as a url points to the file, it can be deployed on the jboss > instance. If that's the case, I'd like to modify the jboss plugin to > support deploying from the deployment destination (i.e., my internal > release repository). > > Kris Bravo > >
