We need BIs mostly for loading of settings and for form editor to analyze
designed components. Possibly also for editing of BeanNodes.
This is slow if the BeanInfo class is in a package enumerated in BI search path
or not defined at all as we can ask all modules to load it for each it on search
Possible tricks to make it faster:
BI in the same package. Not possible for JDK classes or something what should
not be exposed in API/SPI
Reduce number of entries in search paths. Currently there are -
Do not query app CL too often. The dirty trick would be to load some known
resource from packages on search path to warmup the CL cache.
Avoid the need for BI ;-)