You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Vamsavardhana Reddy (JIRA)" <ji...@apache.org> on 2007/11/23 17:13:43 UTC

[jira] Closed: (GERONIMO-3620) Remote deployment using command line deployer does not really work

     [ https://issues.apache.org/jira/browse/GERONIMO-3620?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Vamsavardhana Reddy closed GERONIMO-3620.
-----------------------------------------

    Resolution: Fixed

Part 2 in the issue description is to be addressed in documentation.

> Remote deployment using command line deployer does not really work
> ------------------------------------------------------------------
>
>                 Key: GERONIMO-3620
>                 URL: https://issues.apache.org/jira/browse/GERONIMO-3620
>             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.