Hi. Yes it supports all of 2.5 and JSP 2.1. It is essentially a dispatcher that is compatible with any HttpService. Jsp is supported by a JspServlet that is registered within this dispatcher. The good thing to use an existing HttpService is that both complex web applications and simple "one-servlet" applications (like Felix WebConsole) can co-exists on the same servlet engine.
BR, Sten Roger Sandvik On Wed, Sep 30, 2009 at 4:01 AM, Lin Sun <[email protected]> wrote: > Hi, > > Got a quick question... Does this implementation support Servlets and > JSPs implemented to the Servlet 2.5 and JSP 2.1 specifications or any > later versions of those specifications? I am asking this because I > remember seeing this as required for RFC 66. I was under the > impression that the HttpService only supports servlets but not jsps > but I could be wrong. > > Thanks > > Lin > > On Tue, Sep 29, 2009 at 12:04 PM, Sten Roger Sandvik <[email protected]> wrote: > > Hi. > > > > The implementation is using any HttpService as the http server. Does not > > integrate any server on it's own. When a WAB is registered a > WebApplication > > is buildt. This is then wrapped inside a Servlet and registered on the > > HttpService. I can then implement all features except Session handling. > The > > session handling must either be done by an extension to the HttpService > or > > by implementing a new pluggable session handling for the WebContainer. > > PaxWeb integrates Jetty. But this implementation will be able to use > PaxWeb > > or Felix HttpService or any other http service. > > > > Did that answer the questions? > > > > BR, > > Sten Roger Sandvik > > > > On Tue, Sep 29, 2009 at 5:46 PM, Jeremy Hughes <[email protected]> > wrote: > > > >> Hi, I'm interested - what web container implementation are you > >> integrating? Is your code achieving something similar to Pax Web which > >> integrates Jetty with the HTTPService? An implementation of RFC66 > >> isn't *required* to use the HTTPService, that's one approach. > >> > >> The URL handler that is part of the initial contribution is agnostic > >> of whether the HTTPService is used or not. > >> > >> Thanks, > >> Jeremy > >> > >> > Hi. > >> > > >> > First off I would like to give my support to the Aries project. I > think > >> it > >> > is a really needed project. Looked at some of the talks about RFC66 > >> > (WebContainer) and my understanding is that you will need some sort of > >> WAR > >> > deployer in Aries? Have been working on a RFC66 implementation that > can > >> run > >> > on any OSGi HttpService. This is around 95% feature complete (except > for > >> > session management) right now. Every web applicaiton deployed is added > to > >> > the HttpService as a servlet where alias = context-path. I am not sure > if > >> > this implementation belongs to Felix or Aries. > >> > > >> > What do you guys think? > >> > > >> > BR, > >> > Sten Roger Sandvik > >> > > >
