[
https://issues.apache.org/activemq/browse/CAMEL-1256?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=48784#action_48784
]
William Tam commented on CAMEL-1256:
------------------------------------
A fix has been submitted. Here is some highlights.
* The fix is for 2.0 only since it involves some APIs changes that is an
overkill to keep it backward compatible. Will update wiki.
* It depends on CXF 2.2-SNAPSHOT now. Will upgrade CXF once the next release
of CXF is available.
* CxfBinding, Bus [CAMEL-1239], HeaderFilterStrategy can be looked up from
registry by the "#" notation.
* Decouple CXF Message from Camel Message. That is, users are no longer
required to cast Camel's message body to CXF Message in order to access SOAP
headers and body in PAYLOAD. In PAYLOAD mode, Camel message body now returns a
new type CxfPayload which contains SOAP headers and body. With CxfPayload
being the body in PAYLOAD mode, It makes using Camel converter to convert to
other types pretty easy and transparent.
* Cleaning up the old CxfBinding and "invoking context". Both tried to do
Camel/CXF message binding. CxfBinding is now an interface that an custom impl
can be set on each endpoint. HeaderFilterStrategy impl can also be set on each
endpoint.
* [CAMEL-1254] support serviceClass=#bean
* some major refactoring to make code cleaner.
> Clean up camel-cxf
> ------------------
>
> Key: CAMEL-1256
> URL: https://issues.apache.org/activemq/browse/CAMEL-1256
> Project: Apache Camel
> Issue Type: Improvement
> Components: camel-cxf
> Affects Versions: 1.5.0
> Reporter: William Tam
> Assignee: William Tam
> Fix For: 2.0.0
>
>
> The camel-cxf component is dued for some code cleanup and refactoring. We
> can clean some of of the interfaces and redundant code, etc.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
