[
https://issues.apache.org/jira/browse/AXIS2-3743?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12589368#action_12589368
]
Rich Scheuerle commented on AXIS2-3743:
---------------------------------------
After a closer reading of the specification, the special content id syntax is
only needed for raw SWA attachments (i.e. those defined as message parts).
There is no specific syntax for SWARef ids (i.e. those defined using an element
with {http://ws-i.org/profiles/basic/1.1/xsd}:swaref or JAXB field with
@XmlAttachmentRef() annotation).
Thus this issue will only be used to fix the raw SWA attachment CID.
(Aside: Currently OM does not have a way to specify both the DataHandler and
the CID on an OMText node. This is unfortunate because it would be useful to
include "swaref" in the CID for SWARef attachments and the local name in the
CID for MTOM attachments. I may open a minor issue for this.)
> JAXWS: CID for SWA Attachments does not comply with the WS-I Specification
> Syntax
> ---------------------------------------------------------------------------------
>
> Key: AXIS2-3743
> URL: https://issues.apache.org/jira/browse/AXIS2-3743
> Project: Axis 2.0 (Axis2)
> Issue Type: Bug
> Components: jaxws
> Reporter: Rich Scheuerle
> Assignee: Rich Scheuerle
>
> Background:
> WS-I defines a syntax for SWA attachment content ids. The cid should be
> preceeded by the wsdl:part name.
> http://www.ws-i.org/Profiles/AttachmentsProfile-1.0.html#Value-space_of_Content-Id_Header
> Problem:
> The SWA attachments and SWARef attachments produced and consumed by the JAXWS
> module should abide by WS-I rules.
> If multiple attachments are passed to an endpoint, the partName information
> in the cid should be used to assign the attachment to the corresponding
> field/parameter.
> If the attachment names do not comply with WS-I, the code should fallback to
> the existing algorithm.
--
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]
