J F W

HOW TO : WEBAPP

web.xml (struts 1.x, axis 1.x, tiles 1.x)

UTF-8

For being able to use parameters encoded in UTF-8 have to be added the following filter:

<filter> <filter-name>Charset Filter</filter-name> <filter-class>com.jfw.web.filter.CharsetFilter</filter-class> <init-param> <param-name>requestEncoding</param-name> <param-value>UTF-8</param-value> </init-param> <!-- <init-param> <param-name>excludeUrls</param-name> <param-value>action1.do;action2.do</param-value> </init-param> --> </filter> <filter-mapping> <filter-name>Charset Filter</filter-name> <url-pattern>/*</url-pattern> </filter-mapping>

What “we have said” to Tomcat is to filter all the requests before the elaboration and execute the code in the filter. This filter sets up the encoding for the current request. If we do not want to apply the filter to some actions or jsps we have to:

1. set a more restrictive pattern in url-pattern in tag filter-mapping; the default pattern includes all the urls.
2. Set the excludeUrls init parameter in tag filter-class. See the javadoc of class CharsetFilter for more informations.

Compression

In order to compress the data sent to the browser, the following lines must be added:

<filter> <filter-name>CompressionFilter</filter-name> <filter-class>com.jfw.web.filter.CompressionFilter</filter-class> <init-param> <param-name>compressionThreshold</param-name> <param-value>128</param-value> </init-param> </filter> <filter-mapping> <filter-name>CompressionFilter</filter-name> <url-pattern>*.do</url-pattern> </filter-mapping> <filter-mapping> <filter-name>CompressionFilter</filter-name> <url-pattern>*.jsp</url-pattern> </filter-mapping>

The compression filter is not active in the example webapp.

Axis

To activate Axis the following lines must be added:

<listener> <listener-class>org.apache.axis.transport.http.AxisHTTPSessionListener</listener-class> </listener> <servlet> <servlet-name>AxisServlet</servlet-name> <servlet-class> org.apache.axis.transport.http.AxisServlet </servlet-class> </servlet> <servlet> <servlet-name>ServletAdaptor</servlet-name> <servlet-class>com.sun.ws.rest.impl.container.servlet.ServletAdaptor</servlet-class> <load-on-startup>1</load-on-startup> </servlet> <servlet-mapping> <servlet-name>AxisServlet</servlet-name> <url-pattern>/servlet/AxisServlet</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>AxisServlet</servlet-name> <url-pattern>*.jws</url-pattern> </servlet-mapping> <servlet-mapping> <servlet-name>AxisServlet</servlet-name> <url-pattern>/services/*</url-pattern> </servlet-mapping> <mime-mapping> <extension>wsdl</extension> <mime-type>text/xml</mime-type> </mime-mapping> <mime-mapping> <extension>xsd</extension> <mime-type>text/xml</mime-type> </mime-mapping>

Struts 1.2.9

Here follows the configuration of Struts:

<servlet> <servlet-name>action</servlet-name> <servlet-class>org.apache.struts.action.ActionServlet</servlet-class> <init-param> <param-name>config</param-name> <param-value>/WEB-INF/struts-config.xml</param-value> </init-param> <init-param> <param-name>debug</param-name> <param-value>2</param-value> </init-param> <init-param> <param-name>detail</param-name> <param-value>2</param-value> </init-param> <init-param> <param-name>validate</param-name> <param-value>true</param-value> </init-param> <load-on-startup>2</load-on-startup> </servlet> <servlet-mapping> <servlet-name>action</servlet-name> <url-pattern>*.do</url-pattern> </servlet-mapping> <jsp-config> ... <taglib> <taglib-uri>/tags/struts-tiles</taglib-uri> <taglib-location>/WEB-INF/struts-tiles.tld</taglib-location> </taglib> <taglib> <taglib-uri>/tags/struts-bean</taglib-uri> <taglib-location>/WEB-INF/struts-bean.tld</taglib-location> </taglib> <taglib> <taglib-uri>/tags/struts-html</taglib-uri> <taglib-location>/WEB-INF/struts-html.tld</taglib-location> </taglib> <taglib> <taglib-uri>/tags/struts-logic</taglib-uri> <taglib-location>/WEB-INF/struts-logic.tld</taglib-location> </taglib> ... </jsp-config>

Usually, the requests sent to Struts for being elaborated are those that end in ".do". In order to change this behavior, the value of tag url-pattern must be changed in servlet-mapping.

Scheduler

This is a JFW component and in order to be activated the following lines must be added:

<servlet> <description>start the scheduler</description> <servlet-name>scheduler</servlet-name> <servlet-class>com.jfw.scheduler.StartSchedulerServlet</servlet-class> <load-on-startup>3</load-on-startup> </servlet> <servlet-mapping> <servlet-name>scheduler</servlet-name> <url-pattern>/servlet/StartScheduler</url-pattern> </servlet-mapping>

In order to startup the scheduler, if it is not possible to modify the web.xml file, the method start of the class SchedulerStarter can be called.

JFW tag library

This is a JFW component and in order to be activated the following lines must be added:

<jsp-config> ... <taglib> <taglib-uri>/tags/mytaglib</taglib-uri> <taglib-location>/WEB-INF/mytaglib.tld</taglib-location> </taglib> ... </jsp-config>

This is the tag library definition of JFW. For the moment, only the definition of tag generic used by the parser implemented in the class exists. Parser.