[
https://jira.jboss.org/jira/browse/RF-7947?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Nick Belaevski updated RF-7947:
-------------------------------
Workaround Description: use a4j:include instead.
Workaround: [Workaround Exists]
> Richfaces javascript failure when using jsp:include on jspx file
> ----------------------------------------------------------------
>
> Key: RF-7947
> URL: https://jira.jboss.org/jira/browse/RF-7947
> Project: RichFaces
> Issue Type: Bug
> Affects Versions: 3.3.2.GA
> Environment: JBoss AS 5.1.0.GA
> Richfaces 3.3.2.GA (3.3.1.GA also affected)
> Reporter: Shadow Creeper
> Assignee: Nick Belaevski
> Fix For: Future
>
> Attachments: test.jsp, test.jspx
>
>
> If you have a jsp:include of a jspx file, then Richfaces fails to put the
> javascript resources in the head.
> Using jsp:include of jsp (or jsf) files is no problem, only including jspx
> files kills the Richfaces components.
> Said jspx file need not contain any rich: or a4j: components.
> If you remove the jsp:include, or replace it with an a4j:include, the
> javascript resources work again. However, sometimes a4j:include is not
> desired. I have a rich:toolbar which I would like to jsp:include a file with
> the rich:toolbarGroup, and a4j:include fails due to rich:toolbarGroup no
> longer being direct child of rich:toolbar.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
richfaces-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/richfaces-issues
