Hi John,
Indeed, you specify a module ID in geronimo-web.xml (if you are
working on a Web app). You need to use the following construct:
<environment>
<moduleId>
<groupId>whatEverMakeSenseToYou</groupId>
<artifactId>whatEverMakeSenseToYou</artifactId>
<version>DeveloperA-Version</version>
<type>war</type>
</moduleId>
</environment>
Each developer needs to have their own copy of geronimo-web.xml with
a distinct module ID.
Thanks,
Gianny
On 24/08/2006, at 1:22 AM, John wrote:
Thank you Gianny,
One question, Where do I specify module ID for each developer? in
their copy of geronimo-web.xml in their own dedicated repository
directory?
Making progress...
John
On Wed, 23 Aug 2006 22:16:26 +1000, Gianny Damour
<[EMAIL PROTECTED]> wrote:
Hello John,
Here is a quick summary of how this could work.
Out-of-the-box, Geronimo uses var/config/config.xml to identify the
modules to be loaded upon start-up and also to override the out-of-
the-box configuration of these modules (for instance, virtual hosting
can be overridden in this configuration file).
As each developer needs to have full control of the modules that they
want to start along with their configurations, each developer needs
to have a dedicated config.xml. Also, each developer needs to have
their own copy of the var directory. This copy can be rooted wherever
you want. You can use one of the two following system properties to
specify where this copy is located:
1. org.apache.geronimo.server.name: this property specifies the
relative path of the cloned var folder.
2. org.apache.geronimo.home.dir: this property specifies the full
path of the cloned var folder.
Whatever the method used, each developer needs to put their own
config.xml file in var/config. At least, each developer should be
allocated with dedicated HTTP, JMS et cetera ports and their
config.xml should mirror this allocation. Note that you cannot simply
allocate a virtual host to each developer.
Developers sharing the same server share the same Geronimo
repository, i.e. the repository folder. This implies that a developer
can see the modules deployed by other developers and can also
override them. So, I think each developer should be allocated with a
dedicated moduleId to prevent the override problem.
I may be wrong but I believe it is possible to add a dedicated
repository for each developer. Perhaps that someone else can comment
further.
Thanks,
Gianny
On 22/08/2006, at 10:41 PM, John Larsen wrote:
Hello!
I am adding to existing question I found in the archives.
Basically I am trying to see how I can host Geronimo to developers
on shared servers.
I understand you can share files and config for Geronimo for
multiple instances. But what I don't understand is how this works.
Tell me if I am correct.
There is a main instance with its own var dir with general config
and standard ports.
Then the var dir gets duplicated for each instance and dropped in
the WEB-INF dir for each instance with their own configured port
numbers?
Then does virtual hosts for tomcat need to be setup in the main
instance config for each since each instance will have its own
domain name.
Finally will each domain be able to have their own login to
Geronimo to deploy their applications without seeing or effecting
other instances?
Thank you for you time!
John
--
John
JavaPipe.com
