[
https://issues.jboss.org/browse/RF-12000?page=com.atlassian.jira.plugin.s...
]
Jean ANDRE commented on RF-12000:
---------------------------------
Thank you very much.
I've updated the conversation: [Tab Panel backing bean isolation / attach data on tab
/ Bean
initialization?|https://community.jboss.org/message/809305#809305]
We tried to migrate from 4.2.3 to 4.3.1 but we failed because of significant change into
4.3.1. This version is not back compatible and we need to adapt the code and figure out
why some links does not perform anymore and so on... We are in production, not the right
time to upgrade.
It will be nice for us having this bug solved or having some guide line or
recommendations.
-
https://java.net/jira/browse/JAVASERVERFACES-2016
-
https://issues.jboss.org/browse/RF-12907
We have found clues about the problem, but not enough to understand the whole case. We do
not have the time to debug third party stuff.
Is there a migration guide from 4.2.3 to 4.3.1 ? Until the version 4.2.3 we had success in
following your continuous upgrade but not this time. Sorry.
TabPanel - Backing bean initialization when a same bean manages
multiple dynamic tabs
-------------------------------------------------------------------------------------
Key: RF-12000
URL:
https://issues.jboss.org/browse/RF-12000
Project: RichFaces
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: component-panels-layout-themes
Reporter: Jean ANDRE
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
--
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