sorted by: recent | see : popular

Content Tagged with WTP + jetty

Application servers and servlet containers host other "applications", which leads to complexities involving classloaders. This makes logging setup difficult given the various use cases that may be desired. Some may want a single choice of logger and configuration for the entire application server or servlet container. Others may want each webapp to have their own choice of logger and logging configuration. Typically, each use case requires a different configuration of the server. This is why WTP has largely punted on this issue. Thus, at the current time, logging configuration is left as an exercise for the user. Since Preview Server (i.e. Jetty) is using the full commons logging 1.0.4 jar, the possibilities are somewhat restricted. The suggestion earlier basically implemented the use case of getting commons logging out of the way so each webapp could independently use log4j directly. By configuring commons logging to use SimpleLog, I would expect the commons logging output to go to t

Jetty - Eclipse

Jetty support for WTP

Jetty Server Adaptor Plugin.