geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From David Jencks <djen...@gluecode.com>
Subject Re: [jira] Created: (GERONIMO-357) Command line deployer should be able to connect to remote server
Date Mon, 04 Oct 2004 19:38:03 GMT
My impression is that the 88 tool only works on the same machine as the 
server.  I thought it did not send the module you were deploying over 
the connection but only its location (File). Am I wrong?

thanks
david jencks

On Oct 4, 2004, at 12:27 PM, dev@geronimo.apache.org wrote:

> Message:
>
>   A new issue has been created in JIRA.
>
> ---------------------------------------------------------------------
> View the issue:
>   http://issues.apache.org/jira/browse/GERONIMO-357
>
> Here is an overview of the issue:
> ---------------------------------------------------------------------
>         Key: GERONIMO-357
>     Summary: Command line deployer should be able to connect to remote 
> server
>        Type: Improvement
>
>      Status: Unassigned
>    Priority: Major
>
>     Project: Apache Geronimo
>
>    Assignee:
>    Reporter: Jeremy Boynes
>
>     Created: Mon, 4 Oct 2004 12:27 PM
>     Updated: Mon, 4 Oct 2004 12:27 PM
>
> Description:
> Currently the command line deployer (bin/deployer.jar) works offline 
> by installing configurations directly into the server's config-store.
>
> We support online deployment using the JSR-88 interface by providing 
> the necessary plugin.
>
> It would useful to merge the two and extend the command line deployer 
> so that it can connect to a remote server and deploy things there. The 
> usage of this would be something like:
>
> java -jar bin/deployer.jar
>     --host localhost
>     --user bob
>     --password bob
>     --module myapp.ear
>     --plan myplan.xml
>
> which would construct a JSR-88 url for the server, connect and 
> distribute and start the application.
>
> We should also allow direct specification of the server's connectior 
> url:
> java -jar bin/deploy.jar
>     --server 
> deployer:geronimo:jmx:rmi://localhost/jndi/rmi:/JMXConnector
>     --user bob
>     --password bob
>     --module myapp.ear
>     --plan myplan.xml
>
> just in case other transports are in use.
>
> The converse undeploy operation would also be useful.
>
>
>
> ---------------------------------------------------------------------
> JIRA INFORMATION:
> This message is automatically generated by JIRA.
>
> If you think it was sent incorrectly contact one of the administrators:
>    http://issues.apache.org/jira/secure/Administrators.jspa
>
> If you want more information on JIRA, or have a bug to report see:
>    http://www.atlassian.com/software/jira
>


Mime
View raw message