[
https://issues.apache.org/jira/browse/RAVE-838?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13487736#comment-13487736
]
Matt Franklin commented on RAVE-838:
------------------------------------
I looked at the code and see now what Ate was referring to. We are using the
widget object in 3 places during the render cycle:
1) In the region_widget.tag JSP tag
2) In the RegionWidgetTag.java tag
3) In the OpenSocial Renderer
At this point, my recommendation would be the same as Ate's: Remove the
controller code to get tags and put them into the context in favor of an "on
demand" java tag that adds the specified widget to the context a la
PersonTag.java. I would also update the renderer interface to take a Widget
instance as well as a RegionWidget so that the OpenSocial renderer doesn't have
to go back to the repository for the widget information. This way, the widget
object is requested one time and is passed through the remainder of the render
cycle.
> Performance problems after model-split merge
> --------------------------------------------
>
> Key: RAVE-838
> URL: https://issues.apache.org/jira/browse/RAVE-838
> Project: Rave
> Issue Type: Bug
> Affects Versions: 0.17
> Reporter: Chris Geer
> Assignee: Chris Geer
> Fix For: 0.17
>
>
> - WidgetServer/Repository.get is being called much more frequently with the
> RegionWidget/Widget split.
--
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
