Well, you are assuming that people are using a tool which does the
resolving. Today you can simply download the Apache Felix Jetty bundle,
install and enjoy. No tooling required. With such a proposal we're
breaking this experience
Carsten
Am 19.10.2018 um 16:10 schrieb Raymond Auge:
I know in the past I argued against exposing all the jetty bundles. But I
feel I was probably wrong back then. I think that with the jetty BOM and
the OSGi resolver, figuring out which bundles you need, and then adding
additional ones to suite your case, is not so hard.
Furthermore, Service Loader Mediator is not as painful anymore, just use an
R7 framework with the SpiFly framework extension.
- Ray
On Fri, Oct 19, 2018 at 9:30 AM Raymond Auge <raymond.a...@liferay.com>
wrote:
Why not start relying on the Jetty BOM and let people depend on the
bundles what they want, at least this way they can let the resolver
assemble the bundles they need?
- Ray
On Fri, Oct 19, 2018 at 3:39 AM Carsten Ziegeler <cziege...@apache.org>
wrote:
The other option would be if jetty could provide us one fat bundle, to
avoid having users to install N bundles, it would just be one additional.
Regards
Carsten
Am 19.10.2018 um 09:35 schrieb Carsten Ziegeler:
Hi Eric,
I would like to come back to this discussion; I somehow forgot to
follow
up on the old thread.
If we go with a thin Apache Felix Jetty bundle, then you need to
install
a lot of other bundles even if you don't use http2. So updating from a
current version to this new version is not nice.
How about we still include the jetty bundles inside, fix the service
loader configuration by including it - but do not include the other
things needed for http2 support. So if you're not using http2, it works
like today.
If you use http2 you install additionally spifly and what else is
required to make it work.
Would that work?
Regards
Carsten
Am 18.10.2018 um 19:59 schrieb Eric Norman:
Yes, with a few changes to the felix.http code it is possible to make
it
work.
I stashed the code changes in my github fork at
https://github.com/enapps-enorman/felix which I think you have already
discovered?
I would be willing to initiate a PR from the fork, but unfortunately
the
http/2 support doesn't work without changing how the felix.http bundle
is
packaged as discussed on the felix mailing list at:
https://www.mail-archive.com/users@felix.apache.org/msg18187.html
The felix community seemed reluctant to make the packaging changes to
the
felix.http bundle so I didn't send the PR at the time.
Regards,
Eric
On Thu, Oct 18, 2018 at 10:04 AM Naftali <nvdl...@gmail.com> wrote:
Hi, is there any way to enable enable HTTP/2 support in the embedded
felix
jetty?
Greetz Naftali
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
--
*Raymond Augé* <http://www.liferay.com/web/raymond.auge/profile>
(@rotty3000)
Senior Software Architect *Liferay, Inc.* <http://www.liferay.com>
(@Liferay)
Board Member & EEG Co-Chair, OSGi Alliance <http://osgi.org>
(@OSGiAlliance)
--
Carsten Ziegeler
Adobe Research Switzerland
cziege...@apache.org
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@felix.apache.org
For additional commands, e-mail: users-h...@felix.apache.org
