|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
|
||||||||
|
This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira |
||||||||
The background for this is CPU profiling. When going down this path initially I only "profiled" in terms of overall time taken and the proxying added minimal overhead in that regard. However, it apparently does have some level of impact on the CPU profile.
As far as I see the best/only option is to move to straight implementation+delegation model. The difficulty there is "weaving in" the handling (exception conversion, resource registration, etc) which would need to be done method-by-method (tediousness).