Here is a summary of what I think we discussed on the selectors/servlet thread over the past couple of days. Please chime in of you think something is wrong or missing (like I could stop anyone from doing that...:-)
- we want to have selectors package that contains a useful set of selector examples. - this selectors package will contain some set of selectors, some generic, some specific to certain containers (tomcat, etc). - the selectors package will be packaged separately from the log4j core package and documented as to its "experimental" nature. - really good, detailed documentation should accompany the selector package to give users and understanding of how to use/configure it. Information for configuration with specific containers will be most helpful here. - the ContextClassLoaderSelector (formally Log4jCRS) is a very well written, useful example (thank you, Jacob). Some modifications may be in order and may use it to create a Tomcat 4.1.X specific version (that handles the tomcat specific jsp class loader issue), etc. - Want to include a version of the JNDIRS as well. - we want to include a useful set of web application/servlet related classes. These classes could contain the following types: log4j init servlet, log4j init/shutdown servlet context listener, log4j configuration servlet, various log4j related servlet filters (like a cookie->MDC filter). - these classes will live in their own package (o.a.log4j.servlet?) and will be packaged separately from the log4j core package. - Jacob's Log4jInitServlet and Log4JApplicationWatch are very good starting points. - The servlet classes should be written to be able to use/handle any RepositorySelector. They should not be written to any specific selector. This may require changes in the RepositorySelector interface or may require a different design for the servlet classes. - documentation on how to use/configure a web application to use the servlet classes must be written, with information for specific containers (I'm thinking of the tomcat 4.1.X vs resin 2.1.X issue, servlet 2.2 vs servlet 2.3, etc). - it is hoped that the above activity/implementation will: 1) provide log4j users a very useful set of classes that can be used in various web application containers, something that is lacking in an official form right now. 2) interest and excite web application container implementors to implement log4j specific supporting functionality into their containers (ie RepositorySelectors). Did I miss anything? -Mark -- To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]> For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
