You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@cxf.apache.org by "Aki Yoshida (JIRA)" <ji...@apache.org> on 2013/06/27 12:38:20 UTC

[jira] [Created] (CXF-5095) Allow adding attachments to the contetx using jaxws attachments

Aki Yoshida created CXF-5095:
--------------------------------

             Summary: Allow adding attachments to the contetx using jaxws attachments
                 Key: CXF-5095
                 URL: https://issues.apache.org/jira/browse/CXF-5095
             Project: CXF
          Issue Type: Bug
          Components: JAX-WS Runtime
    Affects Versions: 2.7.5
            Reporter: Aki Yoshida
            Assignee: Aki Yoshida


Currently, it is not possible to add attachments using jaxws's attachments.

http://cxf.547215.n5.nabble.com/Attachments-for-Dispatch-not-supported-td5729017.html

There are some options to get the wiring of attachments (of cxf and jaxws) working.

Option 1
change the WrappedMessageContext's put method so that the cxf's native attachments-set gets added when the jaxws attachments-map is added.
This is probably the simplest approach. But its limitation is that you cannot reflect any change of the original jaxws attachments-map into the actual cxf's attachments-set stored in the context, once this cxf's attachments-set is created and inserted.

Option 2
introduce package local WrappedAttachments that holds the original jaxws's attachments-map and expose it as the cxf's attachments-set. That means, when the jaxws's attachments-map is inserted, WrappedMessageContext can wrap it with WrappedAttachments which is treated as cxf's attachments-set. In this way, any operations on cxf's attachments-set or jaxws' attachments-map remain consistent. 

Option 2 is more flexible than option 1 and prevents potential confusion. So, I think we can choose option 2.





--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira