[
https://issues.apache.org/jira/browse/FELIX-6458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Carsten Ziegeler updated FELIX-6458:
------------------------------------
Description:
ServiceComponentRuntimeImpl currently maintains a cache per bundle (updated by
bundle and service listeners) to have a performant way to create
ServiceReferenceDTOs
Since OSGi R8 , ServiceReference now supports adapting directly to a
ServiceReferenceDTO which would avoid the whole cache.
Downside is that we tie the implementation to R8 - I think this is fine for the
R8 implementation of DS
[~tjwatson] What do you think?
was:
ServiceComponentRuntimeImpl currently maintains a cache per bundle (updated by
bundle and service listeners) to have a performant way to create
ServiceReferenceDTOs
Since OSGi R8 , ServiceReference now supports adapting directly to a
ServiceReferenceDTO which would avoid the whole cache.
Downside is that we tie the implementation to R8
[~tjwatson] What do you think?
> Use ServiceReference.adaptTo(ServiceReferenceDTO)
> -------------------------------------------------
>
> Key: FELIX-6458
> URL: https://issues.apache.org/jira/browse/FELIX-6458
> Project: Felix
> Issue Type: Improvement
> Components: Declarative Services (SCR)
> Reporter: Carsten Ziegeler
> Priority: Major
>
> ServiceComponentRuntimeImpl currently maintains a cache per bundle (updated
> by bundle and service listeners) to have a performant way to create
> ServiceReferenceDTOs
> Since OSGi R8 , ServiceReference now supports adapting directly to a
> ServiceReferenceDTO which would avoid the whole cache.
> Downside is that we tie the implementation to R8 - I think this is fine for
> the R8 implementation of DS
> [~tjwatson] What do you think?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
