[
https://issues.apache.org/jira/browse/CAMEL-4641?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13146418#comment-13146418
]
Claus Ibsen commented on CAMEL-4641:
------------------------------------
Dan
Didn't knew there was a difference between MESSAGE in Camel and MESSAGE in CXF.
But I am not an CXF expert :). Just that the MESSAGE has been this way in Camel
at all time, and that's also what we document on the camel-cxf wiki page etc.
However that said. I also think its the correct way to try to align this so
MESSAGE is the same in Camel and CXF,
and to do this in a major release such as Camel 3.0.
However I wonder if it would be possible to have a RAW mode, for ppl that may
depend currently on the stream directly? Likewise I would anticipate people who
may do WS proxy with Camel, that a pure RAW mode would come handy.
> CxfEndpoint didn't support some kind of feature when dataFormat=MESSAGE
> -----------------------------------------------------------------------
>
> Key: CAMEL-4641
> URL: https://issues.apache.org/jira/browse/CAMEL-4641
> Project: Camel
> Issue Type: Bug
> Components: camel-cxf
> Affects Versions: 2.8.2
> Environment: Win 7, JDK1.6
> Reporter: Xilai Dai
> Assignee: Daniel Kulp
> Fix For: 3.0.0
>
>
> With this camel url setting :
> cxf://http://localhost:8201/airport.service?wsdlURL=file:///D:/wsdl/airport.service.wsdl&dataFormat=MESSAGE
> want to add our cxf feature to CxfEndpoint, Unfortunately, there are about 3
> Phases interceptors have been used in the implementation of our cxf feature.
> Phase.PRE_INVOKE
> Phase.USER_LOGICAL
> Phase.PRE_STREAM
> from the testing result, the interceptors in the cxf feature will be removed.
> When dataFormat=PAYLOAD, it works ok.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
