camel-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "James Strachan (JIRA)" <j...@apache.org>
Subject [jira] Resolved: (CAMEL-121) Support CXF which other different message model
Date Tue, 09 Oct 2007 16:02:24 GMT

     [ https://issues.apache.org/activemq/browse/CAMEL-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

James Strachan resolved CAMEL-121.
----------------------------------

       Resolution: Fixed
    Fix Version/s: 1.2.0

applied by chirino in the revision 576522 at Sep 17.

> 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
>             Fix For: 1.2.0
>
>         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.


Mime
View raw message