geronimo-xbean-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Jarek Gawor (JIRA)" <>
Subject [jira] [Commented] (XBEAN-208) DelegatingBundle performance issues
Date Wed, 22 Aug 2012 15:13:42 GMT


Jarek Gawor commented on XBEAN-208:

Yes, loading a class that does not exist (and is not exported) is the worst case scenario
but there isn't much we can do about that. We have to check all bundles since there is no
way to tell right away if that class can or cannot be loaded.

As to Introspector.getBeanInfo() issues, the code is already optimized for the additional
two BeanInfo lookups. Specifically, in line 173 (which will reject java.lang.ObjectBeanInfo
load) and in line 196 (which will reject sun.beans.infos.<Foo>BeanInfo load).

> DelegatingBundle performance issues
> -----------------------------------
>                 Key: XBEAN-208
>                 URL:
>             Project: XBean
>          Issue Type: Improvement
>          Components: bundleutils
>    Affects Versions: 3.11
>            Reporter: Jarek Gawor
>            Assignee: Jarek Gawor
> DelegatingBundle suffers from some performance issues when loading classes or looking
up resources. 
> The getResource() can be slow because each lookup can cause a lookup on each bundle that
DelegatingBundle delegates to.
> The loadClass() can be slow for the same reason as getResource() and because PackageAdmin
(which can be very slow) is used to lookup a bundle for a given package. 

This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:!default.jspa
For more information on JIRA, see:


View raw message