[
https://issues.apache.org/jira/browse/OWB-1381?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17308546#comment-17308546
]
Romain Manni-Bucau commented on OWB-1381:
-----------------------------------------
[~skybber] it can be solved in OWB at the cost of more caching and memory usage
whereas in integration framework you have this cache anyway by
design/construction so I think it is saner to fix the consumers there since the
misses (it would be a miss cache) can be very numerous with the number of
frameworks trying to lookup beans in CDI before falling back in standalone
mode. I suspect you can add a wrapper to add the cache in the app as a
workaround (short term).
Hope it makes sense.
> Empty resolvedComponents not cached in InjectionResolver
> --------------------------------------------------------
>
> Key: OWB-1381
> URL: https://issues.apache.org/jira/browse/OWB-1381
> Project: OpenWebBeans
> Issue Type: Improvement
> Components: Injection and Lookup
> Affects Versions: 2.0.21
> Reporter: Vladimir Dvorak
> Priority: Minor
>
> YourKit performance analyzer showed that the call of
> InjectionResolver.implResolveByType() could be pretty expensive. The method
> uses caching except the case when no component is found. This case is skipped
> at the end of the metod as is visible at:
> [https://github.com/apache/openwebbeans/blob/master/webbeans-impl/src/main/java/org/apache/webbeans/container/InjectionResolver.java#L559]
>
> In our case we have huge JSF page with a lot of JSF Converters classes, that
> form injectionPointType input argument of the method. It is not clear why JSF
> converters are not found...
>
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
