Versions Compared

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.

...

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

Tip

The use of environment variables is recommended for command-line use.  For example, set REPO2= org.example.configs/myrepo/2.0-SNAPSHOT/car?ServiceModule=org.example.configs/myrepo/2.0-SNAPSHOT/car,j2eeType=ConfigurationStore,name=Local2.

To deploy to the new repository, use: deploy --targets %REPO2% sample.war

...

In the case of multiple server instances, the separate path may be given for the  Maven2Repository root attribute for each server.  To make this easier, a resolveToServer attribute is added to this GBean, so that the root attribute may be set to repository, and it will thus be unique for each server instance with no changes required for each instance, say in config.xml.

Warning

What's lacking is console support for multiple repositories, and support for hot deployment and plugins.

Note

An interesting wrinkle here is in what repository is the new repository deployed?  It's clear that the second repository (say repo2.xml above) will be deployed in the first repository. 

...

Thus, making this first repository read-only will not work for dynamically adding repositories.  Perhaps a second repository is added to contain these server-unique repositories.  The second repository must be shared and read-write, so it does not fit nicely in the use case. (sad)