[ https://issues.jboss.org/browse/RF-13278?page=com.atlassian.jira.plugin.s... ] Brian Leathem edited comment on RF-13278 at 12/20/13 1:19 AM: -------------------------------------------------------------- To recap: The component with id _label_ is rendered during a component tree walk when the visited component has a matching id. If the component is never visited in the tree walk, it is never rendered. There are two means the _label_ component will be visited/rendered in a tree walk: # when the tabPanel is rendered, and the tab headers are rendered # when the tabPanel children/facets are visited Prior to RichFaces 4.3.4, 2) was the case. With every component tree walk, every child of every tab was visited, including those that were not visible. This incurred a significant performance overhead. With the resolution of RF-13107 the visit was prevented for all non-active tabs. This is why the _label_ component is no longer visited unless the tabPanel is an explicit render target. Let's take a look at the performance overhead incurred when tabPanel is a render target. When a tab header is clicked, the active tab (_tabPanel@ActiveItem_) is rendered regardless of the render target. Then the tabPanel is the render target, the active tab panel, and the tab headers are rendered. So the only additional overhead incurred is in the rendering of the tab headers. [~alsha] are you sure you are incurring _ much more performance overhead_ ? Do you have any numbers to back this up? I would presume that you would in fact see a performance increase with 4.3.4 given that the inactive tabs are no longer updated. was (Author: bleathem): To recap: The component with id _label_ is rendered during a component tree walk when the visited component has a matching id. If the component is never visited in the tree walk, it is never rendered. There are two means the _label_ component will be visited/rendered in a tree walk: # when the tabPanel is rendered, and the tab headers are rendered # when the tabPanel children/facets are visited Prior to RichFaces 4.3.4, 2) was the case. With every component tree walk, every child of every tab was visited, including those that were not visible. This incurred a significant performance overhead. With the resolution of RF-13107 the visit was prevented for all non-active tabs. This is why the _label_ component is no longer visited unless the tabPanel is an explicit render target. Let's take a look at the performance overhead incurred when tabPanel is a render target. When a tab header is clicked, the active tab (_tabPanel@ActiveItem_) is rendered regardless of the render target. Then the tabPanel is the render target, the active tab panel, and the tab headers are rendered. So the only additional overhead incurred is in the rendering of the tab headers. [~alsha] are you sure you are incurring _ much more performance overhead_? Do you have any numbers to back this up? I would presume that you would in fact see a performance increase with 4.3.4 given that the inactive tabs are no longer updated. -- 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