You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@wicket.apache.org by "Martin Grigorov (JIRA)" <ji...@apache.org> on 2013/05/21 14:05:16 UTC
[jira] [Resolved] (WICKET-5195) libxml2 splits large CData section.
this breaks the processing of components
[ https://issues.apache.org/jira/browse/WICKET-5195?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Martin Grigorov resolved WICKET-5195.
-------------------------------------
Resolution: Duplicate
Assignee: (was: Igor Vaynberg)
This is fixed in Wicket 6.8.0
> libxml2 splits large CData section. this breaks the processing of components
> ----------------------------------------------------------------------------
>
> Key: WICKET-5195
> URL: https://issues.apache.org/jira/browse/WICKET-5195
> Project: Wicket
> Issue Type: Bug
> Components: wicket
> Affects Versions: 6.7.0
> Environment: Linux Chrome and Windows Chrome
> Reporter: Fridolin Jackstadt
>
> 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;
> In Wicket 6 the issue appears again, in Line 1052 of "wicket-ajax-jquery.js".
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira