The RDC sandbox tag library uses JSP 2.0 tag files for most of its tag implementations. As I move towards a beta release, I think we need more options for logging (maybe a new tag library).
I looked at the log (supported) taglib, but I think the commons-logging and log4j dependencies are not appealing as a taglib author (plus its 1.0). While the log taglib is great for logging in JSPs, and the RDC taglib itself uses commons-logging (only for the sample apps), I think logging in tag files is a different beast. As a tag file author, one would hope to: 1) Add no new dependencies for logging that get pushed out to every webapp that uses the tag(lib) 2) Have a logging scheme that can exist amicably with whatever logger(s) the app author chooses to use 3) Check the status of logging within servlet containers I see an effort in Tomcat towards JDK 1.4 logging (with JULI), and if that is any indicator, I think the servlet containers are doing their best to catch up on any slack that Java logging left behind. It seems that the Java logging APIs might be the best bet here. I'd be interested in opinions about logging, specifically w.r.t tag files. I also wonder how much interest there is in a variant of the log taglib that uses JDK 1.4 logging? I looked at the source, if we keep it as light-weight as the current log taglib, it shouldn't be too much effort. Thanks! -Rahul
