[
https://issues.apache.org/jira/browse/GERONIMO-3963?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12590319#action_12590319
]
Jacques Le Roux commented on GERONIMO-3963:
-------------------------------------------
I did not test it completly, but I suppose that it can work also in an
heterogeneous environment, at least from Windows to Linux. you will then have
to create a directory structure like for instance :
on Windows (default) C:\Program Files\IBM\WebSphere\AppServerCommunityEdition
on Linux C\Program Files\IBM\WebSphere\AppServerCommunityEdition\var\config
The same should also work in reverse side.
Maybe as David Jencks suggested in
http://www.nabble.com/Re%3A-Remote-deployment-using---inPlace-option-p16751482s134.html
it should be better to update the documentation to avoid other bad
experiences. For instance make clear that RMI will not look back at the client
inPlace structure from the server.
Thanks
> Remote deployment using the --inPlace option
> --------------------------------------------
>
> Key: GERONIMO-3963
> URL: https://issues.apache.org/jira/browse/GERONIMO-3963
> Project: Geronimo
> Issue Type: Improvement
> Security Level: public(Regular issues)
> Components: deployment
> Affects Versions: 2.0.x
> Environment: Tested on Windows XP but Linux should be the same except
> the drive constraint
> Reporter: Jacques Le Roux
> Priority: Minor
>
> Remote deployment using the --inPlace option (for a totally exploded EAR with
> exploded and only exploded WARs inside) is only possible if you exactly
> replicate the deployed directory structure on both the client and the server
> machine. If you are on Windows you must even replicate the drive.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
