webapps/opsui/src/main/webapp/WEB-INF/web.xml

<?xml version="1.0" encoding="ISO-8859-1"?>
<web-app xmlns="http://java.sun.com/xml/ns/j2ee"
	 xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
	 xsi:schemaLocation="http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/web-app_2_4.xsd"
	 version="2.4">

	<display-name>opsui</display-name>

	 <!--  
	      There are three means to configure Wickets configuration mode and they are
	      tested in the order given. 
	      1) A system property: -Dwicket.configuration
	      2) servlet specific <init-param>
	      3) context specific <context-param>
	      The value might be either "development" (reloading when templates change)
	      or "deployment". If no configuration is found, "development" is the default.
	-->

	<filter>
		<filter-name>wicket.browser</filter-name>
 		<filter-class>org.apache.wicket.protocol.http.WicketFilter</filter-class>
		<init-param>
			<param-name>applicationClassName</param-name>
			<param-value>org.apache.oodt.pcs.opsui.OpsuiApp</param-value>
 		</init-param>
 	</filter>

 <filter-mapping>
  <filter-name>wicket.browser</filter-name>
	<url-pattern>/*</url-pattern>
 </filter-mapping>
 
  <context-param>
    <param-name>filemgr.working.dir</param-name>
    <param-value>/tmp</param-value>
  </context-param>

  <servlet>
    <servlet-name>DataDeliveryServlet</servlet-name>
    <servlet-class>org.apache.oodt.cas.product.data.DataDeliveryServlet</servlet-class>
  </servlet>
  <servlet>
    <servlet-name>DatasetDeliveryServlet</servlet-name>
    <servlet-class>org.apache.oodt.cas.product.data.DatasetDeliveryServlet</servlet-class>
  </servlet>

  <servlet-mapping>
    <servlet-name>DataDeliveryServlet</servlet-name>
    <url-pattern>/data</url-pattern>
  </servlet-mapping>
  
  <servlet-mapping>
    <servlet-name>DatasetDeliveryServlet</servlet-name>
    <url-pattern>/dataset</url-pattern>
  </servlet-mapping>  
 


</web-app>