Thanks for all the replies which were very useful. I have however a further question about one of the suggested solutions: >So why don't you just shortcut this approach: >make a dummy servlet that will load at startup ( is a configuration job) >that instantiates the Application objects. >You don't need a broker (at least not for this problem) >Sloot. How does one guarantee that the dummy servlet will load at startup? Is there a way that does not imply making for an http request from somewhere else? The "(is a configuration job)" seems to refer to something which I am not aware of. Thanks again, Guillaume
- Re: creation of application wide o... Alex Fernández
- RE: creation of application wi... Alistair Hopkins
- RE: creation of applicatio... romain
- Re: creation of applic... Alex Fernández
- RE: creation of applic... Alistair Hopkins
- Re: creation of applicatio... Craig R. McClanahan
- [ linux + tomcat + oracle ] Why VMM is... Kim soon il
- Re: [ linux + tomcat + oracle ] Wh... Alexandre Augusto Drummond Barroso
- RE: creation of application wide object... Bygrave, Robin
- Re: creation of application wide object... Guillaume Barreau
- Re: creation of application wide o... Alex Fernández
- Re: creation of application wi... Matt Goss
- Re: creation of applicatio... Alex Fernández
- Re: creation of applic... Matt Goss
- Re: creation of application wide object... Intergate
- Re: creation of application wide o... craig mcclanahan
- RE: creation of application wide o... David Rees
- Re: creation of application wide o... Alex Fernández
- Re: creation of application wide object... Peter Brandt-Erichsen
- Re: creation of application wide o... craig mcclanahan