geronimo-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Joe Bohn (JIRA)" <>
Subject [jira] Commented: (GERONIMO-2814) Add a second repository to Geronimo
Date Wed, 04 Jun 2008 17:52:44 GMT


Joe Bohn commented on GERONIMO-2814:

Discussing this with David Jencks on IRC resulted in the following:
- rather than a sample this should be an independent plugin.
- the 2nd repository should be created under var and named repository (var/repository).  This
will make it easy for a user that is creating multiple server instances to pick up the repository
when they make a copy of var and leverage it.
- the plugin should be called something like server-repo to communicate that this plugin is
to create a repository that is server specific.
The typical scenario envisioned for the plugin would be:
djencks: I think the main use of this might be to let you run multiple servers off one installation
[1:03pm] djencks: if the repo is in say var/repository then to create a new server you'd start
[1:03pm] djencks: copying var to my-server/var
[1:04pm] djencks: then you can start the new server with a command line arg IIRC and the repo
will be in an appropriate location
[1:04pm] djencks: so I think having a plugin will support this use case which I imagine will
be the most common

> Add a second repository to Geronimo
> -----------------------------------
>                 Key: GERONIMO-2814
>                 URL:
>             Project: Geronimo
>          Issue Type: New Feature
>      Security Level: public(Regular issues) 
>          Components: deployment
>    Affects Versions: 1.1.x, 2.0-M2
>            Reporter: Ted Kirby
>            Assignee: Joe Bohn
>            Priority: Minor
>             Fix For: Wish List
>         Attachments: GERONIMO-2814-J2EEServerImpl.patch, JIRA-2814-2.0.patch, repo2-1.2-plan.xml,
repo2-111-plan.xml, repo2-ag20-plan.xml, repo2-ag20-plan2.xml, repo2-plugin-sample.patch,, ServerRepository-ag20-plan.xml
> It would be nice to allow for a second repository for applications separate from the
default repository used by geronimo.
> One use case would be for multiple server instances where the geronimo repository would
be read-only, and each server instance would have its own read-write repository.
> I have attached a 2.0 plan for a second repository, called repo2.xml.
> Here is how to use it:
> mkdir <germonimo_home>/repo2
> deploy repo2.xml
> The target names are long and cumbersome:
> >java deployer.jar list-targets
> Available Targets:
>   org.example.configs/myrepo/2.0-SNAPSHOT/car?ServiceModule=org.example.configs/myrepo/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local2
>   org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car?ServiceModule=org.apache.geronimo.configs/j2ee-system/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local
> Use of environment variables recommended for command-line use.
> To deploy to the new repo, use:
> deploy --targets %REPO2% sample.war
> deploy list-modules also gives those long target names on each module.
> However, deploy list-modules %REPO2% gives the accustomed short output.
> >java deployer.jar undeploy  "%REPO2%|geronimo/jsp-examples/1.1.1/war"

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

View raw message