[
https://issues.apache.org/jira/browse/WSCOMMONS-107?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andreas Veithen updated WSCOMMONS-107:
--------------------------------------
Component/s: AXIOM
> MTOMBuilder cannot handle mixed content
> ---------------------------------------
>
> Key: WSCOMMONS-107
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-107
> Project: WS-Commons
> Issue Type: Bug
> Components: AXIOM
> Reporter: Thilina Gunarathne
> Assignee: Thilina Gunarathne
> Priority: Blocker
>
> Creating the Jira according to Syam's mail...
> http://marc.theaimsgroup.com/?l=axis-dev&m=116012901721094&w=2
> Quoting Syam...
> What I mean MTOMStAXSOAPModelBuilder builds soap message incorrectly
> means....
> I have soap message built in the following way.
> <parent>
> <child>
> Attachment text
> <grandchild1>sometext</grandchild1>
> <grandchild2>someothertext</grandchild2>
> </child>
> </parent>
> Note: child element has mixed text i.e. plain text and element text.
> I make attachment text from simple string and make it as MTOM attachment.
> When I receive this message on the server side in the service class, this
> message is being transformed in to
> <parent>
> <child>Attachment text</child>
> <grandchild1>sometext</grandchild1>
> <grandchild2>someothertext</grandchild2>
> </parent>
> I think what you said is right. The MTOMStAXSOAPModelBuilder builder
> Is looking at <xop:Include/> and replacing with OMText's and also appending
> the end tag that is causing me the problem.
> I am getting my attachment text correctly. But when I ask child for
> grandchild1 and grandchild2 it is throwing exception because now the
> grandchild1 and grandchild2 are sub elements of parent.
> By the way the other builder i.e. StAXSOAPModelBuilder is giving me the
> soap message as I expected.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
