On Wed, 2002-09-11 at 02:08, Milt Epstein wrote: > On 11 Sep 2002, Craig Longman wrote: > Back to basics: A servlet container will have a bunch of contexts (aka > web applications), and each context will have a bunch of servlets/JSPs > (where "a bunch of" basically means "one or more").
with ya.
> Each context has
> a web.xml file, where you can specify context parameters, and define
> servlets, and specify init parameters for each such defined servlet
> (as well as lots of other fun stuff). Context parameters are
> specified via context-param tags, (servlet) init parameters are
> specified via init-param tags within a servlet tag.
ok. here it becomes clear i have been:
a) despite my protests to the contrary, confusing ServletContext and
ServletConfig
b) not seen the context-param tag for web.xml
the context-param tag will work quite well for what i want, i should be
able to get the init parameters from there just fine. thanks again.
> > it does. i have no idea why the architects of the whatever spec drives
> > the web.xml were so insistent on being as verbose as they were. doing
> > it the tomcat introspection way seems so sensible, and perfectly
> > flexible at the same time.
>
> Not sure what you're referring to here. Introspection/reflection is
> used to determine what kind of listener is specified in the web.xml file.
yes, i understand that. what i meant was, tomcat does it very cleanly
in allowing attribute name=value pairs in the element itself, then tries
to set that by using a setXXX() in the target object.
maybe its just me, but i'm going crazy with configuration-nightmares,
and missing the obvious. i hope to regain my brain power once i have
things sort-of running.
thanks again for all your help.
--
CraigL->Thx();
Be Developer ID: 5852
signature.asc
Description: This is a digitally signed message part
