http://www.objectsource.com/j2eechapters/Ch21-ClassLoaders_and_J2EE.htm
This might help as a start along the path of ClassLoader enlightenment, which someone will need in order to keep the Singleton beast from snarfing heads. Singletons across WARs within an EAR are bad, from every perspective, but good luck. On May 19, 7:07 am, senny <[email protected]> wrote: > Hey > > We have an EAR project, which contains multiple war projects. Our > current Guice setup is one Injector per war so that we can use a > ServletModule for both of them. The problem we are facing now, is that > we need to share singleton instances between the war files. Since we > have different injectors, we don't have the same singleton scope. Is > there a solution to that problem? Or how would you work around it? > > Cheers, > -- Yves > > -- > You received this message because you are subscribed to the Google Groups > "google-guice" group. > To post to this group, send email to [email protected]. > To unsubscribe from this group, send email to > [email protected]. > For more options, visit this group > athttp://groups.google.com/group/google-guice?hl=en. -- You received this message because you are subscribed to the Google Groups "google-guice" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-guice?hl=en.
