cxf-issues mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Aki Yoshida (JIRA)" <>
Subject [jira] [Commented] (CXF-5095) Allow adding attachments to the contetx using jaxws attachments
Date Thu, 27 Jun 2013 11:42:20 GMT


Aki Yoshida commented on CXF-5095:

Hi Dennis,
yes. This retrieval thing works because of what WrappedMessageContext's handling of jaxws
attarchents retrieval at its getter method, which dynamically creates the jaxws's attachment-map
out of the cxf's attachment-set, which Dan mentioned in the mail thread.

regards, aki

> Allow adding attachments to the contetx using jaxws attachments
> ---------------------------------------------------------------
>                 Key: CXF-5095
>                 URL:
>             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.
> 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:

View raw message