On Tue, 2008-08-19 at 18:19 -0400, Bill Higgins wrote: > Hi, I work on a project (IBM Rational Jazz - http://jazz.net/) where we use > an OSGi (Equinox) server runtime within a JEE server, using the Equinox > Servlet Bridge. > > I prefer the HttpCore API to the Servlet API, so I've written a small > wrapper that allows you to embed an Apache HttpProcessor object in the > Servlet/OSGi environment simply by subclassing a superclass I've created and > registering your object with the OSGi runtime. With this superclass, it's > basically about 2-10 lines of code (depending on how many interceptors you > want to add). > > I'd be happy to contribute this superclass, the OSGi packaging, and an > example application if you would be interested in looking at it and possibly > using it. Please let me know. >
I think we will happily accept contribution of the OSGi packaging code. There is already an open JIRA ticket for that https://issues.apache.org/jira/browse/HTTPCORE-125 Code that requires the Equinox Servlet Bridge to work seems a bit out of scope for me, but I believe we could consider taking it as one of those 'contrib' components provided in source only as reference material. A lot of code start off in the 'contrib' package initially but eventually find its home within officially distributed packages. Does this sound ok to you? Oleg > PS - Here's the first couple of lines of the abstract superclass which > should provide some concrete details on what it provides: > > public abstract class AbstractHandlerWrapperServlet extends HttpServlet > implements HttpRequestInterceptorList, HttpResponseInterceptorList { > > private HttpRequestHandler handler; > private HttpContext parentContext; > private BasicHttpProcessor httpProcessor = new BasicHttpProcessor(); > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
