Details
-
Bug
-
Resolution: Done
-
Critical
-
1.1.0.CR1
-
None
-
None
Description
Firing the ProcessBean events at startup has now become a massive hotspot when portable extensions are installed that inject the bean manager. The TypeSafeBeanResolver cache gets cleared and re-created between each firing, which is very expensive. The beansByType cache which provides a big performance boost when no portable extensions are installed appears to be the main culprit.