| <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"><html lang="en"> |
| <HEAD> |
| |
| <meta name="copyright" content="Copyright (c) IBM Corporation and others 2007. This page is made available under license. For full details see the LEGAL in the documentation book that contains this page." > |
| |
| <META HTTP-EQUIV="Content-Type" CONTENT="text/html; charset=ISO-8859-1"> |
| <META HTTP-EQUIV="Content-Style-Type" CONTENT="text/css"> |
| |
| <LINK REL="STYLESHEET" HREF="../book.css" CHARSET="ISO-8859-1" TYPE="text/css"> |
| <TITLE>Http Service and JSP support</TITLE> |
| |
| <link rel="stylesheet" type="text/css" HREF="../book.css"> |
| </HEAD> |
| <BODY BGCOLOR="#ffffff"> |
| <H1> |
| Http Service and JSP support</H1> |
| <p> |
| Equinox provides support for building and running OSGi based web applications both inside RCP and application server environments. In an OSGi web application use |
| of the <a href="https://docs.osgi.org/javadoc/osgi.cmpn/7.0.0/org/osgi/service/http/HttpService.html">OSGi Http Service</a> replaces the use of web.xml deployment file. The Http Service provides a means to register servlets and resources in a manner |
| more consistent with the dynamic environment in Eclipse where bundles can come and go. |
| </p> |
| <p> |
| The platform SDK comes packaged with <b>org.eclipse.equinox.http.jetty</b>, an implementation of the OSGi Http Service that uses Jetty as its underlying servlet container. This implementation allows customization and |
| <a href="../reference/api/org/eclipse/equinox/http/jetty/JettyConfigurator.html">configuration</a> of many of the server settings important for integration. |
| </p> |
| <p> |
| Java Server Pages play a central role in many java server environments, allowing the presentation of dynamic content. On-the-fly compilation of JSPs |
| is provided by <b>org.eclipse.equinox.jsp.jasper</b>'s <a href="../reference/api/org/eclipse/equinox/jsp/jasper/JspServlet.html">JSPServlet</a>. |
| </p> |
| |
| <h2>Http Service Extension Points</h2> |
| <p> |
| In many cases it's easier to use the more declarative style of interaction provided by the extension registry. To support this usage style |
| <b>org.eclipse.equinox.http.registry</b> provides extension points for |
| <a href="../reference/extension-points/org_eclipse_equinox_http_registry_httpcontexts.html">httpcontexts</a>, |
| <a href="../reference/extension-points/org_eclipse_equinox_http_registry_servlets.html">servlets</a>, and |
| <a href="../reference/extension-points/org_eclipse_equinox_http_registry_resources.html">resources</a> that allow the equivalent |
| registration of web resources in the Http Service. |
| </p> |
| <p> |
| A <a href="../reference/api/org/eclipse/equinox/jsp/jasper/registry/JSPFactory.html">JSP Extension Factory</a> class in <b>org.eclipse.equinox.jsp.jasper.registry</b> provides JSP support for use in conjunction with the |
| <a href="../reference/extension-points/org_eclipse_equinox_http_registry_servlets.html">servlets</a> extension point. |
| </p> |
| |
| </BODY> |
| </HTML> |
