You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@camel.apache.org by "Willem Jiang (JIRA)" <ji...@apache.org> on 2007/09/15 09:08:25 UTC
[jira] Commented: (CAMEL-121) Support CXF which other different
message model
[ https://issues.apache.org/activemq/browse/CAMEL-121?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_40136 ]
Willem Jiang commented on CAMEL-121:
------------------------------------
The patch 121 has some unit tests to show how to create a camel router with different message model.
I will continue to do some clean up work about it task , they are listed in the todo comments of the code.
> Support CXF which other different message model
> -----------------------------------------------
>
> Key: CAMEL-121
> URL: https://issues.apache.org/activemq/browse/CAMEL-121
> Project: Apache Camel
> Issue Type: Sub-task
> Components: camel-cxf
> Reporter: Willem Jiang
> Attachments: 121.patch
>
> Original Estimate: 2 weeks
> Remaining Estimate: 2 weeks
>
> A CXF request message will be handled with a bunch of interceptor, we can dived these different stage message to raw message , payload message, and POJO invocation
> Raw Message
> This message is the fresh message which come from CXF transport, it is not been handled any other interceptors .
> Payload Message
> The message which is marshaled message headers and leave the remain message as StaX stream reader.
> POJO invocation
> The client side request will be marshaled into Java objcets as the POJO invocation finally, we can it a POJO invocation.
> This task just work on to enable the CXF components to deal with RawMessage and Payload Message.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.