I wouldn't mind adding some documentation to it.
Cool. I'll check the stuff in and let you add the documentation. BTW, do you agree with the packages I suggested? Ceki seemed to have some reservations with the o.a.l.appender package. What else should I use?
As an implementation note, what happens if there are two servlet
contexts with the same name? This is completely legal, as the servlet
context's name is optional (null is legal) and not required to be
unique. You might want to use another ID as the key to the context map
in your listener, e.g. the ServletContext object itself, its hashcode,
or what it returns for getResource("/") (the latter is the closest
you'll get to the context path, which is unique for a container
instance.
Yeah, I thought about this as well. I guess it is a matter of choosing something both unique and predictable. It has to be predictable if we are going to add it to a configuration file. Maybe we could just write the context path name and obtain it from getResource("/") like you suggested, but format the result to be simply "MyContext". That way, we can just write the name of the context in configuration.
Jake
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
