You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commons-dev@ws.apache.org by "Rich Scheuerle (JIRA)" <ji...@apache.org> on 2007/08/01 20:34:52 UTC
[jira] Created: (WSCOMMONS-227) Move Attachment object from
MessageContext to the OMDocument
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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
Re: [jira] Created: (WSCOMMONS-227) Move Attachment object from
MessageContext to the OMDocument
Posted by Glen Daniels <gl...@thoughtcraft.com>.
+1, this sounds good to me, Rich.
--Glen
Rich Scheuerle (JIRA) wrote:
> 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 ?
>
>
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
[jira] Resolved: (WSCOMMONS-227) Move Attachment object from
MessageContext to the OMDocument
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ 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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
[jira] Commented: (WSCOMMONS-227) Move Attachment object from
MessageContext to the OMDocument
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12517073 ]
Rich Scheuerle commented on WSCOMMONS-227:
------------------------------------------
I will provide a solution after the Axis2 1.3 release.
> 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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org
[jira] Commented: (WSCOMMONS-227) Move Attachment object from
MessageContext to the OMDocument
Posted by "Rich Scheuerle (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/WSCOMMONS-227?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12534176 ]
Rich Scheuerle commented on WSCOMMONS-227:
------------------------------------------
I still think this is a good idea, but I ran into problems with my initial prototype.
> 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: commons-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: commons-dev-help@ws.apache.org