org.eclipse.scout.sdk/templates/server.war/web.xml

<?xml version="1.0" encoding="UTF-8"?>
<!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>
	<servlet>
		<servlet-name>EquinoxBridge</servlet-name>
		<servlet-class>
			org.eclipse.equinox.servletbridge.BridgeServlet
		</servlet-class>
		<init-param>
			<param-name>enableFrameworkControls</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
		-->
		<init-param>
			<param-name>extendedFrameworkExports</param-name>
			<param-value></param-value>
		</init-param>
		<!--
			Specify alternate 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>
		-->
		<load-on-startup>1</load-on-startup>
	</servlet>
	<servlet-mapping>
		<servlet-name>EquinoxBridge</servlet-name>
		<url-pattern>/*</url-pattern>
	</servlet-mapping>
</web-app>