[ https://issues.jboss.org/browse/RF-12000?page=com.atlassian.jira.plugin.s... ] Jean ANDRE updated RF-12000: ---------------------------- Description: See the conversation : https://community.jboss.org/message/718460#718460 Based on the work done, it is more clear about what we need. When a tabPanel, contains dynamic tabs handle by the same backing-bean (because of the same include xhtml), we need a way, a reliable manner to initialize the backing bean when the user switch from a tab to another tab. It might be a specific tag, as rich:bean init="#{.....initialize(params)}". This tab should be executed first, before any other calls of the backing bean whatever its place inside the xhtml page. If several such tags exist wherever (template, include), they must be executed in their natural order, from the deeper to the top of the page hierarchy. So, what we need is a contextual initialization, because the @PostContruct is not well suitable for that situation. Thank you was: See the conversation : https://community.jboss.org/message/718460#718460 Based on the work done, it is more clear about what we need. When a tabPanel, contains dynamic tabs handle by the same backing-bean (because of the same include xhtml), we need a way, a reliable manner to initialize the backing bean when the user switch from a tab to another tab. It might be a specific tag, as rich:bean init="#{.....initialize(params)}". This tab should be executed first, before any other calls of the backing bean whatever its place inside the xhtml page. If several such tags exist wherever (template, include), they must be executed in their natural order, from the deeper to the top of the page hierarchy. Thank you Forum Reference: https://community.jboss.org/message/718460#718460 (was: https://community.jboss.org/message/718460#718460) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-12000?page=com.atlassian.jira.plugin.s... ] Jean ANDRE updated RF-12000: ---------------------------- Description: See the conversation : https://community.jboss.org/message/718460#718460 Based on the work done, it is more clear about what we need. When a tabPanel, contains dynamic tabs handle by the same backing-bean (because of the same include xhtml), we need a way, a reliable manner to initialize the backing bean when the user switch from a tab to another tab. It might be a specific tag, as rich:bean init="#{.....initialize(params)}". This tab should be executed first, before any other calls of the backing bean whatever its place inside the xhtml page. If several such tags exist wherever (template, include), they must be executed in their natural order, from the deeper to the top of the page hierarchy. So, what we need is a contextual initialization, because the @PostContruct is not well suitable for that situation and also a more simple solution rather trying to do it by the PhaseListener (and what about the context???). Related links around of this feature: - http://www.coderanch.com/t/213757/JSF/java/initialize-backing-bean-before... - http://stackoverflow.com/questions/8132394/backing-bean-initialization - http://www.icefaces.org/JForum/posts/list/13260.page - http://cagataycivici.wordpress.com/2006/06/06/managed_beans_aware_of_the/ - http://boardreader.com/thread/how_to_initialize_a_backing_bean_before_w2n... Thank you was: See the conversation : https://community.jboss.org/message/718460#718460 Based on the work done, it is more clear about what we need. When a tabPanel, contains dynamic tabs handle by the same backing-bean (because of the same include xhtml), we need a way, a reliable manner to initialize the backing bean when the user switch from a tab to another tab. It might be a specific tag, as rich:bean init="#{.....initialize(params)}". This tab should be executed first, before any other calls of the backing bean whatever its place inside the xhtml page. If several such tags exist wherever (template, include), they must be executed in their natural order, from the deeper to the top of the page hierarchy. So, what we need is a contextual initialization, because the @PostContruct is not well suitable for that situation and also a more simple solution rather trying to do it by the PhaseListener (and what about the context???). Related links around of this feature: - http://www.coderanch.com/t/213757/JSF/java/initialize-backing-bean-before... - http://stackoverflow.com/questions/8132394/backing-bean-initialization - http://www.icefaces.org/JForum/posts/list/13260.page - http://cagataycivici.wordpress.com/2006/06/06/managed_beans_aware_of_the/ Thank you Forum Reference: https://community.jboss.org/message/718460#718460 (was: https://community.jboss.org/message/718460#718460) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-12000?page=com.atlassian.jira.plugin.s... ] Jean ANDRE commented on RF-12000: --------------------------------- Hello Brian, Thank you for the idea - We tested it and unfortunately, the event is received after the execution of the <c:forEach items="#{tabsClientController.getTabActivities(tab.id)}" var="activity">. We put the <f:event ...> inside the container that contains the page and the event occurs to late. It seems that getting the data occurs before the page rendering and that makes sense. More over, event does not allow to pass a parameter (but it is not a show stopper). Again, thank you of the idea - I'm going to put a comment about that inside the discussion - Many thanks. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/RF-12000?page=com.atlassian.jira.plugin.s... ] Brian Leathem updated RF-12000: ------------------------------- Fix Version/s: 4.3-Tracking Forum Reference: https://community.jboss.org/message/718460#718460 (was: https://community.jboss.org/message/718460#718460) There is some ongoing work at the moment, investigating using a the UIRepeat mechanism to back the TabPanel, rather than a UIOutput component. This should provide a better mechanism for adding dynamic panels. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira