Re: [jetty-dev] Project proposal: jetty-on-OSGi - support for RFC-66

[Jesse McConnell <jesse.mcconnell@xxxxxxxxx>]

that was my thought, we could get some sandbox development going with
this contribution in mind (not checked in), and so long as we are not
checking anything in that is non-CQ reviewed...or shipping out any
releases using this stuff without it declared in the IP log we are ok
for the transitioning phase..

so long as it is in the sandbox and obeying the rules we should be
fine and as Jeff says, once things land through the CQ process we are
golden, or at least a nice bronze.

jesse

--
jesse mcconnell
jesse.mcconnell@xxxxxxxxx



On Wed, Oct 21, 2009 at 13:07, Jeff McAffer <jeff@xxxxxxxxxxxxxxxxx> wrote:
> Thanks.  Makes sense.  Not sure if that was captured in the project
> proposal.  I may have read it too fast but it appeared as though all of this
> is being contributed to Eclipse.
>
> As for the integration of the JSP fragment, while it does use the JSP
> support that is undergoing IP review, that could be seen as a "works with"
> requirement.  That is, the fragment is there just to integrate support for
> some function that is not (as yet) at Eclipse.  This happens all the time
> where we have an eclipse adapter of some sort to call other code we don't
> ship.  So you could consider putting the fragment etc at Eclipse and getting
> a works with clearance for the reference to the JSP support.  When the JSP
> support gets cleared, then we're all happy.
>
> Just a thought.
>
> Jeff
>
> On 2009-10-21, at 1:49 PM, Jan Bartel wrote:
>
>> Jeff,
>>
>> The jsp libs that jetty uses are not cleared through the IP process yet
>> (see http://dev.eclipse.org/ipzilla/show_bug.cgi?id=3458), so any code
>> that depends on them at the moment cannot be checked into Eclipse. At
>> least, that is my understanding.
>> So, depending on timing, it may be the case that the jsp support fragment
>> from the contribution could not be hosted at eclipse. If, however, the IP
>> for jsp comes through first and the bundle is available from Orbit by the
>> time we would check in the contribution, then the jsp frag code could reside
>> at Eclipse.
>>
>> Jan
>>
>> Jeff McAffer wrote:
>>>
>>> That last para threw me a bit.  Would be good to get some clarification
>>> on what parts are to be at Eclipse.  All the rest of the stuff should not be
>>> part of the proposal or IP process.
>>> Jeff
>>> On 2009-10-21, at 1:30 PM, Jan Bartel wrote:
>>>>
>>>> Thanks Hugues!
>>>>
>>>> This is a significant contribution and certainly helps us achieve better
>>>> osgi/eclipse integration, which is one of our goals in moving to the
>>>> eclipse foundation.
>>>>
>>>> I'll just clarify that the source is actually dual licenced, EPL/Apache
>>>> 2
>>>> (as is the rest of jetty) - Hugues email states that in the
>>>> Introduction,
>>>> although a typo in the Proposed Initial Contribution implies that it is
>>>> only EPL.
>>>>
>>>> If accepted, our intention would be to check this into jetty as a
>>>> top-level
>>>> module of the main jetty build that is released as part of the jetty
>>>> core release. We can host any optional fragments such as jsp support along
>>>> with the other jetty extras and the jetty-hightide distribution at codehaus.
>>>>
>>>> regards
>>>> Jan
>>>>
>>>> Hugues Malphettes wrote:
>>>>>
>>>>> Hi everyone,
>>>>> The jetty team - Jan, Greg and Jesse - have kindly reviewed a possible
>>>>> contribution to the jetty project.
>>>>> Here is the bugzilla for this contribution:
>>>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=292837
>>>>> Below is a complete presentation of the project and a pointer to the
>>>>> suggested initial code.
>>>>> What do you think?
>>>>> Cheers,
>>>>> Hugues
>>>>> ==Abstract
>>>>> The goal of this project is to support jetty running inside an OSGi
>>>>> framework.
>>>>> The project will provide an SDK for eclipse-PDE and an equinox
>>>>> distribution of jetty.
>>>>> It will support web-applications contained inside OSGi bundles.
>>>>> It will support developing and debugging OSGi-web-applications in PDE
>>>>> just like any other OSGi bundles.
>>>>> ==Introduction
>>>>> Jetty on OSGi is a proposed project under the jetty project. Under the
>>>>> dual EPL and Apache Software License 2.0.
>>>>> ==Key objectives
>>>>> - Bootstrap jetty7 inside OSGi.
>>>>> - Support an implementation of the OSGi HttpService deployed on jetty7.
>>>>> - Support OSGi RFC-66 webapps in bundles: package web-applications
>>>>> inside OSGi bundles.
>>>>> - Support OSGi RFC-66 deployment of legacy webapps: dynamically
>>>>> transforms legacy webapps into OSGi-bundles (not jetty specific). A
>>>>> jetty-deployer that is an alternative to the WebAppDeployer in this
>>>>> environment.
>>>>> - Provide a jetty-SDK for eclipse-PDE and support development of
>>>>> web-applications with the OSGi toolkit of the PDE.
>>>>> - Provide a runtime distribution based on equinox of jetty.
>>>>> - Expose a sub-set of jetty's objects as OSGi services for
>>>>> administration and deployments of components specific to jetty.
>>>>> - Provide a migration for jetty-hightide to OSGi.
>>>>> - Coordinate efforts with equinox bundles (jetty support, jsp support)
>>>>> - Expose the setup and management of jetty-server instances in OSGi.
>>>>> ==Technical scope
>>>>> Develop a set of OSGi bundles as required for the runtime. The base of
>>>>> the bundles symbolic-name will be: org.eclipse.jetty.osgi
>>>>> They will depend on the current jetty bundles, the required javax*
>>>>> bundles and 3rd party reference implementations of required standards
>>>>> (jsp-2.1 for example).
>>>>> Develop a set of OSGi bundles that contributes jetty7 runtime
>>>>> configurations. They will depend on the eclipse-platform and
>>>>> eclipse-PDE bundles.
>>>>> ==Other eclipse projects: dependencies, overlaps and coordination:
>>>>> Equinox currently maintains the packaging of jetty6 and jsp support.
>>>>> It provides a bundle that bootstraps jetty6 inside equinox.
>>>>> This bundle hosts the servlet that provide the OSGi HttpService and
>>>>> also gets called by eclipse-RCP for the help pages.
>>>>> We should coordinate our efforts with the equinox team in this area.
>>>>> ==Proposed Initial contribution
>>>>> The initial code contribution is licensed under the EPL and is
>>>>> currently hosted here: http://github.com/intalio/hightide-on-osgi
>>>>> It was entirely developed by an eclipse-member organization, Intalio.
>>>>> The project currently creates the SDK and runtime distribution for
>>>>> jetty-on-osgi.
>>>>> It bootstraps jetty. The jetty server is currently a singleton.
>>>>> Examples demonstrate the running of legacy webapps, webapps contained
>>>>> in bundles, the HttpService, jsp with jstl.
>>>>> Support for RFC-66 is currently limited to defining a webapp with the
>>>>> header "Web-ContextPath".
>>>>> Supporting other OSGi frameworks.
>>>>> The package org.eclipse.jetty.osgi.boot.utils.internal contains some
>>>>> java reflection code to support equinox and apache-felix.
>>>>> Other OSGi frameworks can be supported by implementing the
>>>>> corresponding java interfaces and setting them with a fragment hosted
>>>>> by the org.eclipse.jetty.osgi.boot bundle.
>>>>> Inserting additional dependendencies into org.eclipse.jetty.osgi.boot
>>>>> It is possible to customize the set of libraries available to jetty's
>>>>> servers via 2 mechanisms:
>>>>> #1  create a fragment bundle hosted by org.eclipse.jetty.osgi.boot
>>>>> that depends on those new bundles.
>>>>> #2  via jettyhome: jetty servers are configured via the usual
>>>>> jettyhome folder; jars placed inside ${jetty.home}/lib/ext are loaded
>>>>> as part of the classloader that executes jetty.
>>>>> ==Pending CQs: support for jsp and other features:
>>>>> jsp support is part of RFC-66. It is also supported by equinox.
>>>>> Supporting jsp in this project depends on the pending CQ about
>>>>> glassfish-jasper-jsp.
>>>>> Some of the examples depend on other third party libraries: for
>>>>> example the test-jndi webapp.
>>>>> There is no direct links to those libraries in the code of the
>>>>> examples so instructions could be provided for the user to download
>>>>> those libraries.
>>>>> All code related to jsp support is isolated in a single fragment
>>>>> bundle. Installing this bundle enables JSP support.
>>>>> The current prototype also supports an apache felix-based distribution.
>>>>> The donated code depends purely on libraries distributed by eclipse;
>>>>> as a consequence there is no jsp support in the contributed code and
>>>>> no jndi example code.
>>>>> _______________________________________________
>>>>> jetty-dev mailing list
>>>>> jetty-dev@xxxxxxxxxxx
>>>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>>>
>>>> --
>>>> Jan Bartel, Webtide LLC | janb@xxxxxxxxxxx | http://www.webtide.com
>>>> _______________________________________________
>>>> jetty-dev mailing list
>>>> jetty-dev@xxxxxxxxxxx
>>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>>
>>> _______________________________________________
>>> jetty-dev mailing list
>>> jetty-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>>
>> --
>> Jan Bartel, Webtide LLC | janb@xxxxxxxxxxx | http://www.webtide.com
>> _______________________________________________
>> jetty-dev mailing list
>> jetty-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>
> _______________________________________________
> jetty-dev mailing list
> jetty-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/jetty-dev
>