[
https://issues.apache.org/jira/browse/WSCOMMONS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Rich Scheuerle resolved WSCOMMONS-227.
--------------------------------------
Resolution: Won't Fix
After discussion at ApacheCon, Deepal, Glen, and I decided that Axiom should
stay "xml-centric".
We agreed that modeling of attachments to the OM tree requires some work, but
combining them in an a wrapper SOAPMessage or OMDocument
is not the solution.
The Axis2 MessageContext (or other consumer code) should make the connection
between Axiom tree and the attachments at the "Message Context" level.
> Move Attachment object from MessageContext to the OMDocument
> ------------------------------------------------------------
>
> Key: WSCOMMONS-227
> URL: https://issues.apache.org/jira/browse/WSCOMMONS-227
> Project: WS-Commons
> Issue Type: Improvement
> Components: AXIOM
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
>
> Problem:
> The Axis2 MessageContext contains an OM SOAPEnvelope and an Attachments
> object.
> The message is the combination of these two objects.
> It would be beneficial if the Attachments object was attached to its OM tree.
> Proposal:
> Store the Attachments object on the OMDocument. (i.e.
> OMDocument.getAttachments() method)
> Change the Axis2 MessageContext to delegate to the OMDocument to access the
> Attachments map instead of using a local reference
> Change the MTOMStAxSOAPModelBuilder to delegate to the OMDocument to access
> the Attachments map instead of using a local copy.
> These are minor changes.
> Comments ?
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
