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

ASF GitHub Bot commented on CXF-7269:
-------------------------------------

GitHub user JiriOndrusek opened a pull request:

    https://github.com/apache/cxf/pull/278

    [CXF-7269]schemavalidate failed when use mtom and Provider

    cherry-picked from e81a5c953173abb072372ff28e68ba4fd17dc653 and 
08c9194ce2c567ebfe59f59ee628b1197d90fd43
    
    BZ: https://bugzilla.redhat.com/show_bug.cgi?id=1458058
    Upstream (7.0): https://issues.jboss.org/browse/JBEAP-11397


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

    $ git pull https://github.com/JiriOndrusek/cxf CXF-7269-backport

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

    https://github.com/apache/cxf/pull/278.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 #278
    
----
commit fc76e8a8e14e7d83dbea06e3d7b7d8ff48be07fb
Author: JiriOndrusek <jondr...@redhat.com>
Date:   2017-06-06T16:23:33Z

    [CXF-7269]schemavalidate failed when use mtom and Provider
    
    cherry-picked from e81a5c953173abb072372ff28e68ba4fd17dc653 and 
08c9194ce2c567ebfe59f59ee628b1197d90fd43

----


> schemavalidate failed when use mtom and  Provider
> -------------------------------------------------
>
>                 Key: CXF-7269
>                 URL: https://issues.apache.org/jira/browse/CXF-7269
>             Project: CXF
>          Issue Type: Bug
>            Reporter: Freeman Fang
>            Assignee: Freeman Fang
>             Fix For: 3.1.11, 3.2.0
>
>
> The schemavalidate failed during write in XMLStreamDataWriter caused by the 
> extra <xop:Include> element when mtom enabled, we will run into this when use 
> the Provider server.
> We should add a ErrorHandler in XMLStreamDataWriter, similar as we already do 
> for the DataWriterImpl(jaxb case)



--
This message was sent by Atlassian JIRA
(v6.3.15#6346)

Reply via email to