sorted by: recent | see :
popular
Content Tagged with WTP + eclipse
Introduction to Web Services Tools in WTP
http://live.eclipse.org/node/251
Converting a Java project to a Dynamic Web project in Eclipse - GreatWebGuy
Cambiar el tipo de un proyecto en eclipse
Getting started with JSF, Facelets, Eclipse WTP and Tomcat - TheArcMind.com
Getting started with JSF, Facelets, Eclipse WTP and Tomcat
[#MECLIPSE-264] Support for WTP2.0 - jira.codehaus.org
Sample configuration to create a web-nature eclipse project with WTP 2.0 and J2EE dependencies turned on (those under WEB-INF/lib):
<project>
<build>
<plugins>
<plugin> <groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-eclipse-plugin</artifactId>
<configuration>
<wtpapplicationxml>true</wtpapplicationxml>
<wtpversion>2.0</wtpversion>
</configuration>
</plugin>
</plugins>
</build>
</project>
[news.eclipse.webtools] Re: J2EE Preview Server, Jetty, Dynamic Web Proj
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
Page 1 | Next >>