[
https://issues.apache.org/jira/browse/CXF-3235?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12978999#action_12978999
]
Christian Schneider commented on CXF-3235:
------------------------------------------
The first implementation where I noticed this is camel-jms together with
camel-cxf. I guess that at the moment almost all other implementations do not
support the spec.
The problem is in any case that people will want to introduce this gradually at
any bigger installation. So imagine a big company with a service that is used
by 10 clients. If the service upgrades to be spec compliant then all clients
will break. So even if all want to upgrade they will not do it at the same
time.
> Introduce a switch for the soap/jms spec transport to turn of
> SoapJMSInInterceptor
> ----------------------------------------------------------------------------------
>
> Key: CXF-3235
> URL: https://issues.apache.org/jira/browse/CXF-3235
> Project: CXF
> Issue Type: Improvement
> Reporter: Christian Schneider
> Fix For: 2.3.2
>
>
> The soap/jms spec requires several jms properties like SOAPJMS_contentType to
> be set on an incoming message. In case the required properties are not
> present a fault is returned.
> While this is perfectly compliant with the spec it creates interop problems
> with implementations that do not yet follow the spec.
> So I propose to introduce a switch that disables the SoapJMSInInterceptor or
> that turns the faults into warnings. This would allow older clients to
> interoperate with cxf.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
