RE: [Springframework-developer] Re: [Springframework-user] applicationContext.xml for servlet 2.2

[<jue...@we...>]

Darren,

Thanks for the testing. Note that Log4J initialization should happen =
*before* loading the root application context, as any custom =
configuration would not apply for ContextLoader etc else.

Anyway, I've already split Log4jConfigListener into Log4jWebConfigurer, =
Log4jConfigListener, and Log4jConfigServlet (the latter two just =
delegating to the former). This should work nicely, and I consider it =
cleaner to offer separate initialization servlets for Log4J and the root =
context. Spring doesn't depend on Log4J at all, as it uses Commons =
Logging. So one shouldn't be forced to co-initialize Log4J and the root =
context in a Servlet 2.2 container.

I'll commit them today, so they should be both in the com.interface21 =
source tree and the new module by tomorrow.

Regards,
Juergen



-----Original Message-----
From: dar...@hs... [mailto:dar...@hs...]
Sent: Tuesday, August 12, 2003 10:27 AM
To: j=FCrgen h=F6ller [werk3AT]
Cc: spr...@li...
Subject: Re: [Springframework-developer] Re: [Springframework-user]
applicationContext.xml for servlet 2.2




J=FCrgen,

As promised, here's a minor update to the file I sent last night (mainly
javadoc).  I've tested this only in WebSphere 4.0.4 on Windows.
applicationContext, webAppRootKey and Log4J initialisation are handled
appropriately.  Correct exceptions and behaviour are observed if config
files (applicationContext.xml, log4j.properties) are missing or invalid.

Regards,

Darren Davison
CIBM Intranet Team
int> 799 19431
ext> +44 (0)20 7991 9431

(See attached file: ContextLoaderServlet.java)


_____________________________________________________

This transmission has been issued by a member of the HSBC Group=20
"HSBC" for the information of the addressee only and should not be=20
reproduced and / or distributed to any other person. Each page attached=20
hereto must be read in conjunction with any disclaimer which forms part=20
of it. Unless otherwise stated, this transmission is neither an offer =
nor the=20
solicitation of an offer to sell or purchase any investment. Its =
contents are=20
based on information obtained from sources believed to be reliable but
HSBC makes no representation and accepts no responsibility or liability =
as to its completeness or accuracy.