Skip to main content
aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
Diffstat (limited to 'features/org.eclipse.equinox.server.servletbridge/rootfiles/web.xml')
-rw-r--r--features/org.eclipse.equinox.server.servletbridge/rootfiles/web.xml65
1 files changed, 65 insertions, 0 deletions
diff --git a/features/org.eclipse.equinox.server.servletbridge/rootfiles/web.xml b/features/org.eclipse.equinox.server.servletbridge/rootfiles/web.xml
new file mode 100644
index 000000000..e5dbb96e2
--- /dev/null
+++ b/features/org.eclipse.equinox.server.servletbridge/rootfiles/web.xml
@@ -0,0 +1,65 @@
+<?xml version="1.0" encoding="UTF-8"?>
+<!DOCTYPE web-app PUBLIC "-//Sun Microsystems, Inc.//DTD Web Application 2.2//EN" "http://java.sun.com/j2ee/dtds/web-app_2_2.dtd">
+<web-app id="WebApp">
+ <servlet id="bridge">
+ <servlet-name>equinoxbridgeservlet</servlet-name>
+ <display-name>Equinox Bridge Servlet</display-name>
+ <description>Equinox Bridge Servlet</description>
+ <servlet-class>org.eclipse.equinox.servletbridge.BridgeServlet</servlet-class>
+ <init-param>
+ <param-name>commandline</param-name>
+ <param-value>-console</param-value>
+ </init-param>
+ <init-param>
+ <param-name>enableFrameworkControls</param-name>
+ <param-value>true</param-value>
+ </init-param>
+ <!--
+ You can specify your own framework launcher here.
+ The default is: org.eclipse.equinox.servletbridge.FrameworkLauncher
+ <init-param>
+ <param-name>frameworkLauncherClass</param-name>
+ <param-value>org.eclipse.equinox.servletbridge.FrameworkLauncher</param-value>
+ </init-param>
+ -->
+ <!--
+ When the framework is deployed, an extension bundle must be present to allow the Servlet API to
+ be exported by the container. Typically, this extension bundle is created at deploy time by the
+ FrameworkLauncher. If, however, an extension bundle (with id 'org.eclipse.equinox.servletbridge.extensionbundle') is
+ already present in the 'plugins' area, then preference is given to the existing bundle.
+ If this param is set to 'true', then the existing extension bundle with be *overridden* and
+ the one created by the FrameworkLauncher will replace any existing one. The default is 'false'
+ (giving preference to the existing extension bundle if present).
+
+ default: false
+ <init-param>
+ <param-name>overrideAndReplaceExtensionBundle</param-name>
+ <param-value>false</param-value>
+ </init-param>
+ -->
+ <!--
+ org.eclipse.equinox.servletbridge and the Servlet API are exported automatically to the underlying OSGi framework.
+ The extendedFrameworkExports parameter allows the specification of additional java package exports.
+ The format is a comma separated list of exports as specified by the "Export-Package" bundle manifest header.
+ For example: com.mycompany.exports; version=1.0.0, com.mycompany.otherexports; version=1.0.0
+
+ NOTE: This property is ignored by default and is only processed if overrideAndReplaceExtensionBundle is true.
+ <init-param>
+ <param-name>extendedFrameworkExports</param-name>
+ <param-value></param-value>
+ </init-param>
+ -->
+ <load-on-startup>1</load-on-startup>
+ </servlet>
+ <servlet-mapping>
+ <servlet-name>equinoxbridgeservlet</servlet-name>
+ <url-pattern>/*</url-pattern>
+ </servlet-mapping>
+ <!--
+ This is required if your application bundles expose JSPs.
+ -->
+ <servlet-mapping>
+ <servlet-name>equinoxbridgeservlet</servlet-name>
+ <url-pattern>*.jsp</url-pattern>
+ </servlet-mapping>
+</web-app>

Back to the top