On 19/09/17 13:28, RayD wrote:
Question relating to the use of the start attribute on the Content-Type
Header which appears to have been dropped from CXF somewhere along the way.
According to https://tools.ietf.org/html/rfc2387
<https://tools.ietf.org/html/rfc2387> , start is an optional attribute and
I would have expected it to be supported for multipart/related content
types.
3.2. The Start Parameter
The start parameter, if given, is the content-ID of the compound
object's "root". If not present the "root" is the first body part in
the Multipart/Related entity. The "root" is the element the
applications processes first.
I also found this link which suggests that it was dropped from the
specification as was considered redundant (however this was for
multipart/mixed which would make sense and not multipart/related).
https://issues.apache.org/jira/browse/CXF-4348
<https://issues.apache.org/jira/browse/CXF-4348>
Yes, this changes related to that issue were about making the 'start'
not needed for non multipart/related multipart types...
Anyone know why this is no longer supported for multipart/related ?
FYI am using CXF version 3.1.7.
Are you seeing 'start' being not available for multipart/related with
JAX-RS or JAX-WS ? Can you try 3.1.13 ?
Sergey
--
Sent from: http://cxf.547215.n5.nabble.com/cxf-user-f547216.html
