You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@activemq.apache.org by Christopher Shannon <ch...@gmail.com> on 2015/08/19 22:57:12 UTC
Jetty 9.2 OSGi upgrade
I've finished all the work for the Jetty 9.2 upgrade, except for the OSGi
piece. The web console and demo work all of the WebSocket support has been
converted to the new APIs. I've also fixed all of the tests in the http
module that were relying on the old Jetty APIs.
However, the karaf integration tests don't work and it looks like Karaf
might need to be upgraded to make it compatible with Jetty 9, or some work
will need to be done to make Jetty 9 work in the older version of Karaf we
are using (2.4). For example, the pax-web-features which is part of Karaf
appears to be too old.
My OSGi experience is pretty limited so I was wondering if there was anyone
with more OSGi experience who might volunteer to take a look at this
piece? I was thinking about creating a new Jira subtask for the OSGi piece.
Thanks,
Chris
Re: Jetty 9.2 OSGi upgrade
Posted by Christopher Shannon <ch...@gmail.com>.
Quick update on this...
I had some time to look more into this and I was able to upgrade to Karaf 4
(as well as associated dependencies). I went through and fixed all of the
karaf integration tests and started everything up successfully. I won't
have time the rest of this week but I should be able push up the Jetty
commit along with the OSGi changes sometime early next week.
On Thu, Aug 20, 2015 at 9:24 AM, Christopher Shannon <
christopher.l.shannon@gmail.com> wrote:
> Right, and I imagine an upgrade like that will cause all kinds of other
> problems that will need to be resolved. I tried updating to Karaf 4 and
> some other dependencies and it looks like Blueprint was pulled out by
> default. I added Blueprint back but when the tests run the
> CommandProcessor that gets injected can't be found. I'm not really sure
> what's changed in Karaf 4 that needs updating to make everything work again.
>
> On Wed, Aug 19, 2015 at 5:05 PM, Daniel Kulp <dk...@apache.org> wrote:
>
>> Likely needs to move to Karaf 4. Karaf 4 is the first version to
>> support Jetty 9.
>>
>> Dan
>>
>>
>>
>> > On Aug 19, 2015, at 4:57 PM, Christopher Shannon <
>> christopher.l.shannon@gmail.com> wrote:
>> >
>> > I've finished all the work for the Jetty 9.2 upgrade, except for the
>> OSGi
>> > piece. The web console and demo work all of the WebSocket support has
>> been
>> > converted to the new APIs. I've also fixed all of the tests in the http
>> > module that were relying on the old Jetty APIs.
>> >
>> > However, the karaf integration tests don't work and it looks like Karaf
>> > might need to be upgraded to make it compatible with Jetty 9, or some
>> work
>> > will need to be done to make Jetty 9 work in the older version of Karaf
>> we
>> > are using (2.4). For example, the pax-web-features which is part of
>> Karaf
>> > appears to be too old.
>> >
>> > My OSGi experience is pretty limited so I was wondering if there was
>> anyone
>> > with more OSGi experience who might volunteer to take a look at this
>> > piece? I was thinking about creating a new Jira subtask for the OSGi
>> piece.
>> >
>> > Thanks,
>> > Chris
>>
>> --
>> Daniel Kulp
>> dkulp@apache.org - http://dankulp.com/blog
>> Talend Community Coder - http://coders.talend.com
>>
>>
>
Re: Jetty 9.2 OSGi upgrade
Posted by Christopher Shannon <ch...@gmail.com>.
Right, and I imagine an upgrade like that will cause all kinds of other
problems that will need to be resolved. I tried updating to Karaf 4 and
some other dependencies and it looks like Blueprint was pulled out by
default. I added Blueprint back but when the tests run the
CommandProcessor that gets injected can't be found. I'm not really sure
what's changed in Karaf 4 that needs updating to make everything work again.
On Wed, Aug 19, 2015 at 5:05 PM, Daniel Kulp <dk...@apache.org> wrote:
> Likely needs to move to Karaf 4. Karaf 4 is the first version to support
> Jetty 9.
>
> Dan
>
>
>
> > On Aug 19, 2015, at 4:57 PM, Christopher Shannon <
> christopher.l.shannon@gmail.com> wrote:
> >
> > I've finished all the work for the Jetty 9.2 upgrade, except for the OSGi
> > piece. The web console and demo work all of the WebSocket support has
> been
> > converted to the new APIs. I've also fixed all of the tests in the http
> > module that were relying on the old Jetty APIs.
> >
> > However, the karaf integration tests don't work and it looks like Karaf
> > might need to be upgraded to make it compatible with Jetty 9, or some
> work
> > will need to be done to make Jetty 9 work in the older version of Karaf
> we
> > are using (2.4). For example, the pax-web-features which is part of
> Karaf
> > appears to be too old.
> >
> > My OSGi experience is pretty limited so I was wondering if there was
> anyone
> > with more OSGi experience who might volunteer to take a look at this
> > piece? I was thinking about creating a new Jira subtask for the OSGi
> piece.
> >
> > Thanks,
> > Chris
>
> --
> Daniel Kulp
> dkulp@apache.org - http://dankulp.com/blog
> Talend Community Coder - http://coders.talend.com
>
>
Re: Jetty 9.2 OSGi upgrade
Posted by Daniel Kulp <dk...@apache.org>.
Likely needs to move to Karaf 4. Karaf 4 is the first version to support Jetty 9.
Dan
> On Aug 19, 2015, at 4:57 PM, Christopher Shannon <ch...@gmail.com> wrote:
>
> I've finished all the work for the Jetty 9.2 upgrade, except for the OSGi
> piece. The web console and demo work all of the WebSocket support has been
> converted to the new APIs. I've also fixed all of the tests in the http
> module that were relying on the old Jetty APIs.
>
> However, the karaf integration tests don't work and it looks like Karaf
> might need to be upgraded to make it compatible with Jetty 9, or some work
> will need to be done to make Jetty 9 work in the older version of Karaf we
> are using (2.4). For example, the pax-web-features which is part of Karaf
> appears to be too old.
>
> My OSGi experience is pretty limited so I was wondering if there was anyone
> with more OSGi experience who might volunteer to take a look at this
> piece? I was thinking about creating a new Jira subtask for the OSGi piece.
>
> Thanks,
> Chris
--
Daniel Kulp
dkulp@apache.org - http://dankulp.com/blog
Talend Community Coder - http://coders.talend.com