[
https://issues.apache.org/jira/browse/AXIS2-4524?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13041583#comment-13041583
]
Leon Fleysher commented on AXIS2-4524:
--------------------------------------
Do you guys think that a temporary workaround could be opening the adb jar into
a directory and putting it in the classpath -- as I understood from AXIS2-4878
most of the time goes on scanning the axis2 jar(s) for non-existing bean info.
Or may be providing the optional bean info can help?
If none of the above -- may be moving to JAXB data binding can help resolving
this problem?
> 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]
