[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [equinox-dev] JSP support in the servlet bridge incubator project
- From: Harald Niesche <harald@xxxxxxxxxxxxxxxxxxx>
- Date: Fri, 02 Jun 2006 09:40:13 +0200
- Delivered-to: email@example.com
- User-agent: Thunderbird 220.127.116.11 (Windows/20060308)
Richard Backhouse wrote:
> I felt that instead of having
> to prefix all my JSP requests with "/jasper-jsp" it would be preferable
> to support JSP's just as requests for static resources are handled.
> 1.) Created a org.apache.jasper bundle containing the required Jasper
> jars to run the JSP Container (commons-el.jar, jasper-compiler.jar,
> jasper-compiler-jdt.jar and jasper-runtime.jar). This bundle is also a
> fragment bundle whose bundle host is
> org.eclipse.equinox.servlet.bridge.http bundle. This allows references
> to the Jasper classes to be made without having to add explicit imports
> to the org.eclipse.equinox.servlet.bridge.http manifest.
Sounds like you are avoiding a circular reference here.
> The manifest for the
> org.eclipse.equinox.servlet.bridge.extensionbundle was also modified to
> filter the javax.servlet.jsp classes down from the running webcontainer.
Does this mean that you are exposing the servlet api through the
If yes, wouldn't it make more sense to expose them through the
> to be created as standard OSGi bundles. They register their provided
> TLD's via a TldProvider service I added to the
> org.eclipse.equinox.http.registry bundle.
Wouldn't it make sense to register the JSPs in the same way?
> Thoughts ?
Having no fixed prefix like "/jasper-jsp/" sounds great but I wonder if
this approach can be extended to work with any HttpService. I believe
several people here said they liked to test their bundles in a
standalone OSGi runtime using either the Jetty-based HttpService or the
Equinox HttpService while deploying using the bridge servlet.
For me it would actually be a requirement that I retain the freedom to
choose which HttpService is used.