[
https://issues.apache.org/jira/browse/AXIS2-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006581#comment-13006581
]
Andreas Veithen commented on AXIS2-4524:
----------------------------------------
@Martin: As explained above, the natural solution is to put this cache into a
context or description that has the same lifecycle as the service class loader.
Anything else will either lead to memory leaks or make the design unnecessarily
complex.
> Caching BeanInfo in adb module's BeanUtil improves performance
> --------------------------------------------------------------
>
> Key: AXIS2-4524
> URL: https://issues.apache.org/jira/browse/AXIS2-4524
> Project: Axis2
> Issue Type: Improvement
> Components: adb
> Affects Versions: 1.5
> Reporter: Valgeir Halldórsson
> Attachments: BeanUtil.diff, axis2.diff
>
>
> I've detected that org.apache.axis2.databinding.utils.BeanUtil class can be
> improved for performance. It seems that invoking
> Introspector.getBeanInfo(Class, Class) takes a lot of time. By caching
> java.beans.BeanInfo in this class it doubles up (at least) the performance,
> especially when returning a big dataset. I changed this myself and saw a
> great deal of performance improvement.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
