[richfaces-issues] [JBoss JIRA] (RF-11694) RF4 : Bad rendering on rich:dataTable inside ui:include enclosed in a rich:tabPanel
[
https://issues.jboss.org/browse/RF-11694?page=com.atlassian.jira.plugin.s...
]
Jean ANDRE commented on RF-11694:
---------------------------------
A link to read: http://community.jboss.org/message/633448
Fron our side, we put tab in server mode switchType="server" and it is working
but we lost the benefice of the ajax. Probably, one way to resolve this issue it allowing
the capability to declare our-self which resource to download as we did for the datatable
(*.ecss, *.js) when the include is used or another way is having an a4j:include that will
downloaded the desired components.
the <a4j:outputPanel>, seems to play a greater role than we think - Different
behaviors were observed and also with tabPanel and dynamic tabs - The presence or the
absence of this tag may or may not trigger the getActiveItem NPE - Then outputPanel tag is
probably not innocent...
See also the comment for RF-11054 and related (bug with the getActiveItem)
RF4 : Bad rendering on rich:dataTable inside ui:include enclosed in a
rich:tabPanel
-----------------------------------------------------------------------------------
Key: RF-11694
URL: https://issues.jboss.org/browse/RF-11694
Project: RichFaces
Issue Type: Bug
Security Level: Public(Everyone can see)
Components: component-tables
Affects Versions: 4.0.0.Final
Environment: Websphere 8 - RAD 8 - JSF Mojorra 2.1.4 - Spring 3.0.6 Final - Use
@Inject @Named @SessionScoped as annotations - Firefox 7.0.1 - Windows 7 (6.1 sp1)
Reporter: Jean ANDRE
Fix For: 4.Future
Attachments: After F5 Key.jpg, Newly dynamic tab.jpg, Screen at the
beginning....jpg
The rich:dataTable is not rendering with CSS style when the dataTable is inside a
separate file (ui:include src=....) during the ajax rendering on a dynamic insert of
rich:tab.
The error does not appear when the content of the include file is directly moved inside
the final page, I mean without ui:include.
--
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