geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Vamsavardhana Reddy (JIRA)" <>
Subject [jira] Commented: (GERONIMO-3620) Remote deployment using command line deployer does not really work
Date Wed, 21 Nov 2007 10:08:43 GMT


Vamsavardhana Reddy commented on GERONIMO-3620:


I am crippled at building trunk coz my laptop will crash while building geronimo-system module.
 So, I have not built trunk recently.  Shiva hinted about your fix, after which I looked up
the revision and merged it into branches\2.0.  The fix will still need to handle contextPath
"/" as well as remoteDeployAddress ending in "/".


> Remote deployment using command line deployer does not really work
> ------------------------------------------------------------------
>                 Key: GERONIMO-3620
>                 URL:
>             Project: Geronimo
>          Issue Type: Bug
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 2.0.1, 2.0.2, 2.0.x, 2.1
>            Reporter: Vamsavardhana Reddy
>            Assignee: Vamsavardhana Reddy
>             Fix For: 2.0.x, 2.1
> Remote deployment using command line deployer tool does not really work currently as
the host has to be localhost.  Here are my observations.
> 1.  Deployer.getRemoteDeployUploadURL() is not checking if the contextPath starts with
a '/' thus resulting in an incorrect URL like http://localhost:8080//remote-deploy/upload.
> 2. Using a remoteDeployAddress like http://localhost:8080 with hostname localhost is
not useful at all. When the host we are deploying to is the local machine itself, RemoteDeploymentManager.isSameMachine()
returns true and in this case the local files are used directly.

This message is automatically generated by JIRA.
You can reply to this email to add a comment to the issue online.

View raw message