[jira] [Updated] (FELIX-6488) Optimize ServiceReference.isAssignableTo

2022-05-19 Thread Karl Pauls (Jira)


 [ 
https://issues.apache.org/jira/browse/FELIX-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated FELIX-6488:
--
Fix Version/s: framework-7.0.5
   (was: framework-7.0.4)

> Optimize ServiceReference.isAssignableTo
> 
>
> Key: FELIX-6488
> URL: https://issues.apache.org/jira/browse/FELIX-6488
> Project: Felix
>  Issue Type: Improvement
>  Components: Framework
>Affects Versions: framework-7.0.3
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>Priority: Major
> Fix For: framework-7.0.5
>
>
> The ServiceReference.isAssignableTo(Bundle bundle, String className) does 
> some complicated check to see if the service is assignable. This includes 
> trying to load classes and catching CNFE to see if providers and/or 
> requesters have access to the given class. 
> As that is done quite a bit (it is used in service event dispatching and 
> service lookup) it would be good to optimize this to either not throw CNFE 
> during the lookup or maybe at least cache the results to not have them be 
> done all the time. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)


[jira] [Updated] (FELIX-6488) Optimize ServiceReference.isAssignableTo

2022-05-26 Thread Karl Pauls (Jira)


 [ 
https://issues.apache.org/jira/browse/FELIX-6488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Pauls updated FELIX-6488:
--
Fix Version/s: framework-7.0.6
   (was: framework-7.0.5)

> Optimize ServiceReference.isAssignableTo
> 
>
> Key: FELIX-6488
> URL: https://issues.apache.org/jira/browse/FELIX-6488
> Project: Felix
>  Issue Type: Improvement
>  Components: Framework
>Affects Versions: framework-7.0.3
>Reporter: Karl Pauls
>Assignee: Karl Pauls
>Priority: Major
> Fix For: framework-7.0.6
>
>
> The ServiceReference.isAssignableTo(Bundle bundle, String className) does 
> some complicated check to see if the service is assignable. This includes 
> trying to load classes and catching CNFE to see if providers and/or 
> requesters have access to the given class. 
> As that is done quite a bit (it is used in service event dispatching and 
> service lookup) it would be good to optimize this to either not throw CNFE 
> during the lookup or maybe at least cache the results to not have them be 
> done all the time. 



--
This message was sent by Atlassian Jira
(v8.20.7#820007)