[
https://issues.apache.org/jira/browse/MYFACES-2831?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12890493#action_12890493
]
Cagatay Civici commented on MYFACES-2831:
-----------------------------------------
PrimeFaces is migrating to native JSF 2 ajax apis in 2.2 release so if f:ajax
implementation of MyFaces is working, it will mean Primefaces will work as well
as a result since PF will use MyFaces implementation in this case.
> Avoid neested CDATA section for PPR e.g. with Primefaces
> --------------------------------------------------------
>
> Key: MYFACES-2831
> URL: https://issues.apache.org/jira/browse/MYFACES-2831
> Project: MyFaces Core
> Issue Type: Improvement
> Components: JSR-314
> Affects Versions: 2.0.2-SNAPSHOT
> Reporter: Marcus Büttner
> Attachments: MYFACES-2831.patch
>
>
> In PPR with Primefaces a neested CDATA section is rendered for components
> with script sections. I attached a patch for the HtmlResponseWriterImpl in
> myfaces-shared which avoid the double rendering of the CDATA section.
> Primefaces uses startCDATA and endCDATA of ResponseWriter for it's cdata
> section. I've overridden this two methods to memorise if a cdata section is
> open.
> If a cdata section is open it's not opened a second one. I added this check
> to the writeScriptContent() method because there occurse the problem with
> Primefaces.
> Please review the patch because I'm not sure if there are any site effects.
> Thanks,
> Regards Marcus
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
