From: Jan B. <ja...@mo...> - 2006-03-20 23:26:59
|
Hi Mark, >>In the meanwhile, I am working on the whole jasper/"jesper" issue and the >>commons-logging dependency. As "jesper" does not require commons-logging, >>then the plugin could, in theory, do without providing any slf4j impl at all. >>However, that would mandate that users would need to use jdk1.5 (as jesper is >>jsp 2.1 which requires jdk1.5). I don't think that is reasonable at this stage, >>so I need to provide a way for users to specify with a <configuration> option >>whether they want to use jsp2.1 or jsp2.0. If the former, then users can put >>whatever logging they like on the classpath. If the latter, then I need a mechanism >>to detect whether an slf4j impl is already on the classpath, and if not, provide a >>default one that the plugin will downloaded at runtime (if not already in the >>local repo of course). > > > I'm not aware of "jesper" - is this some branch of jasper? There's a thread on jetty-discuss with subject "Jasper JSP for Jetty6!". It's not a branch as such. We just check out Jasper and apply some patches to it to remove the commons-logging. We'll be shipping that with jetty6 and it requires jdk1.5 as it is for jsp2.1. We'll also ship the current version of Jasper that commons-logging in it for jsp2.0. The start.jar mechanism (for standalone jetty) will work out which jdk you are using and automatically put the right version of jasper on the classpath for you. > So does > jetty itself use the slf4j api directly and jcl is only required by > jasper? In which case would jcl104-over-slf4j and slf4j-api suffice, > leaving the user to supply a slf4j impl? Although I seem to recall > Ceki saying a plain slf4j-api jar doesn't exist as such yet. Jetty itself has no dependency on any log infrastructure other than its own (see org.mortbay.log.Log). The jetty log implementation decides at runtime whether to delegate to the slf4j interface if it can find an slf4j impl on the classpath, or failing that, to do its own logging. Jasper is the only thing with a dependency on a logging infrastructure. As for leaving the user to select a log implementation for the plugin, I'd much rather have it work straight out of the box, but allow the user to configure a different slf4j logging delegate if they want. cheers Jan > > Mark > > > ------------------------------------------------------- > This SF.Net email is sponsored by xPML, a groundbreaking scripting language > that extends applications into web and mobile media. Attend the live webcast > and join the prime developer group breaking into this new coding territory! > http://sel.as-us.falkag.net/sel?cmd=k&kid0944&bid$1720&dat1642 > _______________________________________________ > Jetty-support mailing list > Jet...@li... > https://lists.sourceforge.net/lists/listinfo/jetty-support > |