You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@activemq.apache.org by "ASF GitHub Bot (JIRA)" <ji...@apache.org> on 2016/09/22 20:17:20 UTC

[jira] [Commented] (ARTEMIS-747) Multiple CDATA events during import fails

    [ https://issues.apache.org/jira/browse/ARTEMIS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15514367#comment-15514367 ] 

ASF GitHub Bot commented on ARTEMIS-747:
----------------------------------------

GitHub user jbertram opened a pull request:

    https://github.com/apache/activemq-artemis/pull/791

    ARTEMIS-747 multiple CDATA events on import fails

    

You can merge this pull request into a Git repository by running:

    $ git pull https://github.com/jbertram/activemq-artemis ARTEMIS-747

Alternatively you can review and apply these changes as the patch at:

    https://github.com/apache/activemq-artemis/pull/791.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

    This closes #791
    
----
commit 5838b2c11c0776303f912e4738d6ac4448d22988
Author: jbertram <jb...@apache.com>
Date:   2016-09-16T15:25:08Z

    ARTEMIS-747 multiple CDATA events on import fails

----


> Multiple CDATA events during import fails
> -----------------------------------------
>
>                 Key: ARTEMIS-747
>                 URL: https://issues.apache.org/jira/browse/ARTEMIS-747
>             Project: ActiveMQ Artemis
>          Issue Type: Bug
>    Affects Versions: 1.4.0
>            Reporter: Justin Bertram
>            Assignee: Justin Bertram
>
> Message bodies are written to XML as Base64 encoded CDATA elements. Some parser implementations won't read the entire CDATA element at once (e.g. Woodstox) so it's possible for multiple CDATA events to be combined into a single Base64 encoded string.  You can't decode bits and pieces of each CDATA.  Each CDATA has to be decoded in its entirety.  The current importer doesn't deal with this properly.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)