[
http://jira.codehaus.org/browse/MJBOSS-3?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=130730#action_130730
]
PeteJohlie commented on MJBOSS-3:
---------------------------------
Hello
I am having this same problem.
I do not see a resolution, or I do not understand the one presented.
I am trying to use continuum on linux to deploy to a remote linux (not
mountable on continuum/local file system).
What do I use for "repo.server.domain" in this?
<fileName>http://repo.server.domain/path-to-artifact/filename-ear-version.ear</fileName>
===
This is the error I get:
Caused by: java.io.IOException: Server returned HTTP response code: 500 for
URL:
http://vm-dev-apps.gocsc.com:8080/jmx-console/HtmlAdaptor?action=invokeOpByName&name=jboss.system:service%3DMainDeployer&methodName=deploy&argType=java.net.URL&arg0=file://opt/continuum-1.1/apps/continuum/webapp/WEB-INF/working-directory/11/target/hw-0.0.8-SNAPSHOT.war
===
Any info wold be appreciated
Thanks
> JBoss: Slight modification supports deployment to remote jboss instance.
> ------------------------------------------------------------------------
>
> Key: MJBOSS-3
> URL: http://jira.codehaus.org/browse/MJBOSS-3
> Project: Maven 2.x JBoss Plugin
> Issue Type: Improvement
> Environment: maven 2.0.1
> Reporter: Corridor Software Developer
> Assignee: Corridor Software Developer
> Fix For: 1.3.2
>
> Attachments: jboss-remote.patch
>
>
> The jboss plugin uses the jmx deployment interface to perform deployments.
> Currently only local deployments can be done and the code is biased towards
> that end.
> With a slight modification and the help of the mvn deploy goal, we can
> support remote deployment as well. The use case would be "developer deploys a
> j2ee artifact to a remote development jboss instance". The command would be:
> mvn deploy jboss:deploy
> The initial deploy is required because remote deployment requires that the
> server can reach the artifact via a url, and a file:// url isn't sufficient.
> The code change to the deployer is a simple check for an existing protocol in
> the url given from the configuration. If it's not present, prepend "file://".
> This avoids damaging the existing local deployment support.
> The configuration would appear as such:
> <plugin>
> <groupId>org.codehaus.mojo</groupId>
> <artifactId>jboss-maven-plugin</artifactId>
> <configuration>
> <server>server.id</server>
> <hostName>server.domain<hostName>
>
> <fileName>http://repo.server.domain/path-to-artifact/filename-ear-version.ear</fileName>
> <port>port</port>
> </configuration>
> </plugin>
> I'll attach a patch and commit the change soon.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
