Because both instances share the same repository, I guess it's as designed. The only difference would be as followed:
1. on the instance you deployed the application, such as 8080 port by default, config.xml was updated with its moduleId as <module name="com/yourcompany/foo/1.0/car"> 2. while on another instance, the module info was written into config.xml as well, but with the following info <module name="com/yourcompany/foo/1.0/car" load="false"> Anything incorrect with my understanding, please chime in. Jeff C On Wed, Aug 19, 2009 at 6:13 PM, Lu Jiang <jad...@hotmail.com> wrote: > > Environment: > Windows+JDK6+Geronimo2.2 > > I setted up another server instance besides the default one. The defaut one > is on 8080,and the other on 8090.They both work well and share the same > repository. > > If I deploy an application on one server instance,for example, the 8080 > one,then it'll be simultaneously deployed on the 8090 server instance.This > action changes the config.xml of both the default one and the new server > instance. After that ,I tried to deploy the same application to the 8090 > instance. It failed and warned that the application already exists. > > I wonder ,in the case of multiple server instances,if an application is > deployed on one server instance,should the other server instances share > the > application? > -- > View this message in context: > http://www.nabble.com/Different-server-instances-on-Geronimo-2.2-tp25041402s134p25041402.html > Sent from the Apache Geronimo - Users mailing list archive at Nabble.com. > >
