It probably depends on how you have it configured. The main thing to remember is that J2EE uses multiple classloaders and each classloader can potentially have it's own version of a "singleton".
> -----Original Message----- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED]] On Behalf Of > Justin Crosbie > Sent: Monday, 21 January, 2002 8:13 PM > To: Orion-Interest > Subject: RE: Integrating LOG4J into Orion... > > > Hi, > > We have wrapped Log4J in a singleton, so the first call to it > initialises it. I'm not sure if this is a good idea or not > though, but we've had no problems so far. Any opinions? > > -Justin > > -----Original Message----- > From: Romen Law [mailto:[EMAIL PROTECTED]] > Sent: 20 January 2002 23:05 > To: Orion-Interest > Subject: Re: Integrating LOG4J into Orion... > > > ello, > > What I did was to have a initialising SLSB and let the > startup servlet call it. It works for me. > > cheers > romen > > ----- Original Message ----- > From: "Alex Paransky" <[EMAIL PROTECTED]> > To: "Orion-Interest" <[EMAIL PROTECTED]> > Sent: Saturday, January 19, 2002 12:34 PM > Subject: FW: Integrating LOG4J into Orion... > > > > One more time, the last one did not show up.... > > > > -----Original Message----- > > From: Alex Paransky [mailto:[EMAIL PROTECTED]] > > Sent: Thursday, January 17, 2002 11:09 AM > > To: Orion-Interest > > Subject: Integrating LOG4J into Orion... > > > > > > I have a full EJB/JSP application running with Orion. Is there a > preferred > > method of initializing LOG4J in this situation? > > > > Looking at the LOG4J documentation, they mention using a startup > > servlet > to > > do the initialization. I am concerned as to how this would > work with > > the CLASSLOADER hierarchy. If I initialize my LOG4J at the servlet > > (WEB) > layer, > > will the EJB's be able to see the initialized LOG4J or will they > > attempt > to > > re-initialize due to the different classloader? > > > > Thanks. > > -AP_ > > > > > > > >
