You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Tina Umlandt (JIRA)" <ji...@apache.org> on 2010/02/25 11:57:27 UTC
[jira] Created: (WICKET-2759) libxml2 splits large CData section.
this breaks the processing of components
libxml2 splits large CData section. this breaks the processing of components
----------------------------------------------------------------------------
Key: WICKET-2759
URL: https://issues.apache.org/jira/browse/WICKET-2759
Project: Wicket
Issue Type: Bug
Components: wicket
Affects Versions: 1.4.5
Environment: Linux Chrome
Reporter: Tina Umlandt
If the AJAX-Responses in WebKit-Browsern are too large the libxml2 splits the CData-Sections in two: one with 300 chars and the other section with the rest.
This breaks the processComponent function in the wicket-ajax. js because it relies on the fact that only one section is returned:
text = node.firstChild.nodeValue;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Resolved: (WICKET-2759) libxml2 splits large CData section.
this breaks the processing of components
Posted by "Igor Vaynberg (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Igor Vaynberg resolved WICKET-2759.
-----------------------------------
Resolution: Fixed
Fix Version/s: 1.5-M1
1.4.7
Assignee: Igor Vaynberg
thanks
> libxml2 splits large CData section. this breaks the processing of components
> ----------------------------------------------------------------------------
>
> Key: WICKET-2759
> URL: https://issues.apache.org/jira/browse/WICKET-2759
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.5
> Environment: Linux Chrome
> Reporter: Tina Umlandt
> Assignee: Igor Vaynberg
> Fix For: 1.4.7, 1.5-M1
>
>
> If the AJAX-Responses in WebKit-Browsern are too large the libxml2 splits the CData-Sections in two: one with 300 chars and the other section with the rest.
> This breaks the processComponent function in the wicket-ajax. js because it relies on the fact that only one section is returned:
> text = node.firstChild.nodeValue;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Commented: (WICKET-2759) libxml2 splits large CData section.
this breaks the processing of components
Posted by "Tina Umlandt (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WICKET-2759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12838300#action_12838300 ]
Tina Umlandt commented on WICKET-2759:
--------------------------------------
I patched the wicket-ajax.js with the following lines in processComponent line 1300
if (node.hasChildNodes()) {
for( i=0 ; i < node.childNodes.length; i++ ) {
text = text + node.childNodes[i].nodeValue;
}
}
> libxml2 splits large CData section. this breaks the processing of components
> ----------------------------------------------------------------------------
>
> Key: WICKET-2759
> URL: https://issues.apache.org/jira/browse/WICKET-2759
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 1.4.5
> Environment: Linux Chrome
> Reporter: Tina Umlandt
>
> If the AJAX-Responses in WebKit-Browsern are too large the libxml2 splits the CData-Sections in two: one with 300 chars and the other section with the rest.
> This breaks the processComponent function in the wicket-ajax. js because it relies on the fact that only one section is returned:
> text = node.firstChild.nodeValue;
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.