Mapping a servlet to /
An interesting problem cropped up today. We want to use a servlet for the home page in a Spring Web MVC project. Initially we had this in
<servlet> <servlet-name>foo</servlet-name> <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>foo</servlet-name> <url-pattern>*.html</url-pattern> </servlet-mapping>
Now, we want to add in a handler specifically for
/. How to do that? A bit of googling turned up this method.
<servlet> <servlet-name>foo</servlet-name> <servlet-class>org.springframework.web.servlet.DispatcherServlet</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>foo</servlet-name> <url-pattern>*.html</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>foo</servlet-name> <url-pattern>/home</url-pattern> </servlet-mapping> <welcome-file-list> <welcome-file>home</welcome-file> </welcome-file-list>
I’m not 100% sure why this works—the rules for mapping URLs to servlets are a little confusing to me. But it certainly seems to handle the situation correctly. My initial attempts to get this working managed to break everything by handling everything through the DispatcherServlet, even things like CSS. That was unacceptable.
Aha. Looking in the servlet spec shows why:
Web Application developers can define an ordered list of partial URIs called
welcome files in the Web application deployment descriptor.
I had thought that they were files, not URIs. That explains why it works nicely.
Of course, the solution above will attempt to look for “…/home” in any directory, even though I’ve only set it up to work for the root URL. I don’t think that’s much of a problem though.
Tomcat Logging in WTP
I’ve just been trying to enable debug logging for tomcat (don’t ask). Normally you do this by editing
$CATALINA_HOME/conf/logging.properties and restarting.
Except I tried that in Eclipse (using WTP) and it didn’t work.
I tried copying it to the
$CATALINA_BASE/conf directory instead1.
Still no joy.
I’ve just found the answer, after looking in the tomcat source. It turns out that tomcat’s alternative logging implementation (JULI) is enabled via a system property. This happens inside
# Set juli LogManager if it is present if [ -r "$CATALINA_BASE"/conf/logging.properties ]; then JAVA_OPTS="$JAVA_OPTS -Djava.util.logging.manager=org.apache.juli.ClassLoaderLogManager" LOGGING_CONFIG="-Djava.util.logging.config.file=$CATALINA_BASE/conf/logging.properties" fi
But Eclipse runs the Java code directly, without using
catalina.sh. So the properties never gets set. You have to set them by hand in the “Run Configurations” dialog. Like this:
Of note there is that I’ve imported the
logging.properties file into the
Servers project of my workspace. It seemed liked a useful place to put it.
Of course, after realising that, I soon find the same information in the WTP FAQ: How do I enable the JULI logging in a Tomcat 5.5 Server instance?.
Anyway, now I might be able to debug that ClassLoader issue…
1 Inside Eclipse with WTP, that will be something like