aboutsummaryrefslogtreecommitdiff
path: root/pdf-as-web/src/main/webapp/WEB-INF/web.xml
diff options
context:
space:
mode:
Diffstat (limited to 'pdf-as-web/src/main/webapp/WEB-INF/web.xml')
-rw-r--r--pdf-as-web/src/main/webapp/WEB-INF/web.xml101
1 files changed, 101 insertions, 0 deletions
diff --git a/pdf-as-web/src/main/webapp/WEB-INF/web.xml b/pdf-as-web/src/main/webapp/WEB-INF/web.xml
new file mode 100644
index 00000000..13149b7f
--- /dev/null
+++ b/pdf-as-web/src/main/webapp/WEB-INF/web.xml
@@ -0,0 +1,101 @@
+<?xml version="1.0" encoding="ISO-8859-1"?>
+<!DOCTYPE web-app
+ PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.3//EN"
+ "http://java.sun.com/dtd/web-app_2_3.dtd">
+<web-app>
+ <!-- General description of your web application -->
+
+ <display-name>PDF-AS-WEB</display-name>
+ <description>
+ PDF-AS-WEB Application
+ </description>
+
+
+ <!-- Context initialization parameters that define shared String constants
+ used within your application, which can be customized by the system administrator
+ who is installing your application. The values actually assigned to these
+ parameters can be retrieved in a servlet or JSP page by calling: String value
+ = getServletContext().getInitParameter("name"); where "name" matches the
+ <param-name> element of one of these initialization parameters. You can define
+ any number of context initialization parameters, including zero. <context-param>
+ <param-name>webmaster</param-name> <param-value>myaddress@mycompany.com</param-value>
+ <description> The EMAIL address of the administrator to whom questions and
+ comments about this application should be addressed. </description> </context-param> -->
+
+ <!-- Servlet definitions for the servlets that make up your web application,
+ including initialization parameters. With Tomcat, you can also send requests
+ to servlets not listed here with a request like this: http://localhost:8080/{context-path}/servlet/{classname}
+ but this usage is not guaranteed to be portable. It also makes relative references
+ to images and other resources required by your servlet more complicated,
+ so defining all of your servlets (and defining a mapping to them with a servlet-mapping
+ element) is recommended. Servlet initialization parameters can be retrieved
+ in a servlet or JSP page by calling: String value = getServletConfig().getInitParameter("name");
+ where "name" matches the <param-name> element of one of these initialization
+ parameters. You can define any number of servlets, including zero. -->
+
+ <servlet>
+ <servlet-name>SignServlet</servlet-name>
+ <description>
+ The Sign Servlet allows Users to Sign PDF Documents ...
+ </description>
+ <servlet-class>at.gv.egiz.pdfas.web.servlets.SignServlet</servlet-class>
+ <load-on-startup>5</load-on-startup>
+ </servlet>
+ <servlet>
+ <servlet-name>ProvidePDF</servlet-name>
+ <display-name>ProvidePDF</display-name>
+ <description></description>
+ <servlet-class>at.gv.egiz.pdfas.web.servlets.ProvidePDF</servlet-class>
+ </servlet>
+ <servlet>
+ <servlet-name>DataURL</servlet-name>
+ <display-name>DataURL</display-name>
+ <description></description>
+ <servlet-class>at.gv.egiz.pdfas.web.servlets.DataURL</servlet-class>
+ </servlet>
+ <servlet>
+ <servlet-name>VerifyServlet</servlet-name>
+ <display-name>VerifyServlet</display-name>
+ <description></description>
+ <servlet-class>at.gv.egiz.pdfas.web.servlets.VerifyServlet</servlet-class>
+ </servlet>
+
+ <!-- Define mappings that are used by the servlet container to translate
+ a particular request URI (context-relative) to a particular servlet. The
+ examples below correspond to the servlet descriptions above. Thus, a request
+ URI like: http://localhost:8080/{contextpath}/graph will be mapped to the
+ "graph" servlet, while a request like: http://localhost:8080/{contextpath}/saveCustomer.do
+ will be mapped to the "controller" servlet. You may define any number of
+ servlet mappings, including zero. It is also legal to define more than one
+ mapping for the same servlet, if you wish to. -->
+
+ <servlet-mapping>
+ <servlet-name>SignServlet</servlet-name>
+ <url-pattern>/Sign</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>ProvidePDF</servlet-name>
+ <url-pattern>/ProvidePDF</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>DataURL</servlet-name>
+ <url-pattern>/DataURL</url-pattern>
+ </servlet-mapping>
+ <servlet-mapping>
+ <servlet-name>VerifyServlet</servlet-name>
+ <url-pattern>/VerifyServlet</url-pattern>
+ </servlet-mapping>
+
+ <!-- Define the default session timeout for your application, in minutes.
+ From a servlet or JSP page, you can modify the timeout for a particular session
+ dynamically by using HttpSession.getMaxInactiveInterval(). -->
+
+ <session-config>
+ <session-timeout>30</session-timeout> <!-- 30 minutes -->
+ </session-config>
+
+ <welcome-file-list>
+ <welcome-file>signstart.jsp</welcome-file>
+ </welcome-file-list>
+
+</web-app> \ No newline at end of file