You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@felix.apache.org by Thomas Driessen <th...@gmail.com> on 2018/07/16 08:35:49 UTC

Re[2]: ServletContainerInitializer

Hi Carsten, hi Ray,

thanks for your answers.
I've proposed the whiteboard solution to the Vaadin guys.

@Ray
Could you explain your idea? Unfortunatly I can not access this bug 
report.

Kind regards,
Thomas

------ Originalnachricht ------
Von: "Raymond Auge" <ra...@liferay.com>
An: "felix users" <us...@felix.apache.org>
Cc: "Thomas Driessen" <th...@gmail.com>
Gesendet: 13.07.2018 17:31:06
Betreff: Re: ServletContainerInitializer

>
>
>On Fri, Jul 13, 2018 at 11:17 AM, Carsten Ziegeler 
><cz...@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 
>><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
>>cziegeler@apache.org
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: users-unsubscribe@felix.apache.org 
>><ma...@felix.apache.org>
>>For additional commands, e-mail: users-help@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)

Re: Re[2]: ServletContainerInitializer

Posted by Raymond Auge <ra...@liferay.com>.
On Mon, Jul 16, 2018 at 4:35 AM, Thomas Driessen <
thomas.driessen.td@gmail.com> wrote:

> Hi Carsten, hi Ray,
>
> thanks for your answers.
> I've proposed the whiteboard solution to the Vaadin guys.
>
> @Ray
> Could you explain your idea? Unfortunatly I can not access this bug report.
>

Yeah, sorry! The idea is to use the extension dependencies model from
JAX-RS whiteboard [1].

- Ray

[1]
https://osgi.org/specification/osgi.cmpn/7.0.0/service.jaxrs.html#d0e133663


>
> Kind regards,
> Thomas
>
> ------ Originalnachricht ------
> Von: "Raymond Auge" <ra...@liferay.com>
> An: "felix users" <us...@felix.apache.org>
> Cc: "Thomas Driessen" <th...@gmail.com>
> Gesendet: 13.07.2018 17:31:06
> Betreff: Re: ServletContainerInitializer
>
>
>>
>> On Fri, Jul 13, 2018 at 11:17 AM, Carsten Ziegeler <cz...@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/bugz
>> illa/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 <
>>> 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
>>> cziegeler@apache.org
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: users-unsubscribe@felix.apache.org <mailto:
>>> users-unsubscribe@felix.apache.org>
>>> For additional commands, e-mail: users-help@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)
>
>


-- 
*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)