On Fri, Jul 13, 2018 at 11:17 AM, Carsten Ziegeler <cziege...@apache.org> wrote:
> Hi, > > there is no support for ServletContainerInitializer in the OSGi > whiteboard specification and therefore no support in the Apache Felix > implementation. > > Major reason of this is the dynamic nature of OSGi, bundles can come and > go and when a bundle arrives the servlet context might already be > initialized. > Hey Carsten, we've got a model that can handle this scenario and I've already proposed it for R8 (see *Bug 3061* <https://osgi.org/members/bugzilla/show_bug.cgi?id=3061>). The idea is identical to the handling of jaxrs whiteboard's required extensions. Maybe in the next few months, if I have time I can prototype it. - Ray > > Now, the equivalent of this is actually the whiteboard which allows to > dynamically register web resources. > > Regards > > Carsten > > > > Thomas Driessen wrote > > Hi, > > > > I'm following the current development of OSGi support in Vaadin 10/11 > > and found this issue: > > > > https://github.com/vaadin/flow/issues/4376 > > > > Vaadin seems to make use of a ServletContainerInitializer for its Routes > > and it seems not to work with jetty and felix. > > > > Is there support for ServletContainerInitializers in felix.http.jetty or > > the whiteboard? Or is this something that is not supported? > > > > Kind regards, > > Thomas > -- > 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)
