felix-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Raymond Auge <raymond.a...@liferay.com>
Subject Re: memory visibility of @Reference service references
Date Tue, 02 May 2017 17:18:22 GMT
On Tue, May 2, 2017 at 1:14 PM, Raymond Auge <raymond.auge@liferay.com>
wrote:

>
> On Tue, May 2, 2017 at 11:46 AM, Dirk Hogan <dirk.hogan@forgerock.com>
> wrote:
>
>> But no similar guarantee applies when another thread hits the
>> component,
>>
>
> I believe the discussion boils down to why you believe the above is
> possible?
>
> If SCR has not yet made the component available to other threads (which,
> to my knowledge, it only does by registering it as a service to the service
> registry) how can _another_ thread access the component at all?
>
> I don't even see a way for components within the same DS bundle to
> interact with each other other than via the service registry because
> @Reference only works through the registry.
>

Correction, components could interact with each other via the
ComponentContext.. but I guess we'd have to know if that's part of your use
case.

- Ray


>
> Please, can you explain in more detail what case might allow for the
> above? Because I believe the assumption is that it's not currently
> possible. Certainly there could be a bug and I'm certain everyone would
> want to see that fixed.
>
> --
> *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)

Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message