From jira-events at lists.jboss.org Fri Sep 27 08:21:02 2013
Content-Type: multipart/mixed; boundary="===============6368534542679122069=="
MIME-Version: 1.0
From: =?utf-8?q?Jon=C3=A1=C5=A1_Trantina_=28JIRA=29_=3Cjira-events_at_lists=2Ej?=
 =?utf-8?q?boss=2Eorg=3E?=
To: richfaces-issues at lists.jboss.org
Subject: [richfaces-issues] [JBoss JIRA] (RF-13221) Incorrect XML encoding in
 AJAX response
Date: Fri, 27 Sep 2013 08:21:02 -0400
Message-ID: <JIRA.12501466.1380105464000.4174.1380284462610@jira02.app.mwc.hst.phx2.redhat.com>
In-Reply-To: JIRA.12501466.1380105464000@jira02.app.mwc.hst.phx2.redhat.com

--===============6368534542679122069==
Content-Type: text/plain; charset="utf-8"
MIME-Version: 1.0
Content-Transfer-Encoding: quoted-printable


    [ https://issues.jboss.org/browse/RF-13221?page=3Dcom.atlassian.jira.pl=
ugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=3D12807915#com=
ment-12807915 ] =


Jon=C3=A1=C5=A1 Trantina commented on RF-13221:
-------------------------------------

Vanilla JSF behaves exactly the same. Both issues (XML entity and CDATA) ar=
e present.
JSF also displays a dialog message "emptyResponse: An empty response was re=
ceived from the server.  Check server error logs." when reproducing the CDA=
TA issue. Server logs are empty, of course.
                =

> Incorrect XML encoding in AJAX response
> ---------------------------------------
>
>                 Key: RF-13221
>                 URL: https://issues.jboss.org/browse/RF-13221
>             Project: RichFaces
>          Issue Type: Bug
>      Security Level: Public(Everyone can see) =

>    Affects Versions: 4.3.4
>            Reporter: Jon=C3=A1=C5=A1 Trantina
>              Labels: waiting_on_user
>
> Consider the following example:
> {noformat}
> <h:form>
> <a4j:commandButton render=3D"@form" value=3D"rerender me"/>
> <script src=3D"path_to_some_script?param=3Dasd&amp;important=3Dparam"></s=
cript>
> </h:form>
> {noformat}
> when commandButton is clicked, the form is rerendered and the response lo=
oks like this:
> {noformat}
> <partial-response><changes><update id=3D"someID"><![CDATA[
>    ...
>   <script src=3D"path_to_some_script?param=3Dasd&amp;important=3Dparam"><=
/script>
> ]]</ ... >
> {noformat}
> But this is wrong. Because script tag is already in CDATA, so there is no=
 need for XML encoding for '&' entity.
> This further causes script loading to fail (performed by jsf.js), wheneve=
r parameters are needed (e.g. portal environment), =

> because script is downloaded from {noformat}"path_to_some_script?param=3D=
asd&amp;important=3Dparam" {noformat}
> instead of {noformat}"path_to_some_script?param=3Dasd&important=3Dparam"{=
noformat}.
> Another very similar issue is when CDATA element is present in a re-rende=
red fragment. Example:
> {noformat}
> <h:form>
> <a4j:commandButton render=3D"@form" value=3D"rerender me"/>
> <style type=3D"text/css">
> /* <![CDATA[ */
>       .somecssclass {...}
> /* ]] */
> </style>
> </h:form>
> {noformat}
> The AJAX response then looks like so:
> {noformat}
> <partial-response><changes><update id=3D"someID"><![CDATA[
> ...
>    <![CDATA[
>       ...
>   ]]
> ...
> ]]</ ... >
> {noformat}
> And this is incorrect XML, since CDATA cannot contain ']]', so the respon=
se is discarded.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrato=
rs
For more information on JIRA, see: http://www.atlassian.com/software/jira


--===============6368534542679122069==--