cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Glynn, Eoghan" <>
Subject RE: ClientImpl - creates a new message ????
Date Mon, 20 Nov 2006 11:43:31 GMT


The purpose of the Binding.createMessage() call in
ClientImpl.onMessage() is to *wrap* the generic message provided by the
transport layer with a binding-specific message.

Thus for say SOAP over HTTP, the HTTPConduit creates a generic Message
for the incoming payload, which is then wrapped by a SoapMessage created
by the SoapBinding.

This allows for a clean separation between binding and transport in the
incoming dispatch path.

However, things are slightly different for CORBA, as the binding and
transport are one and the same. So why not just implement
CORBABinding.createMessage() as follows:

    public Message createMessage(Message message) {
        // no wrapping required
        return message;


> -----Original Message-----
> From: Nolan, Edell [] 
> Sent: 17 November 2006 16:22
> To:
> Subject: ClientImpl - creates a new message ????
> Hi,
> I am trying to port Yoko over from celtix to use cxf.
> In this use case, a Web services client talks to a Web 
> services server through the IIOP protocol. Both the client 
> and the server are implemented using cxf and the IIOP 
> protocol is enabled by installing the Yoko CORBA binding into cxf.
> The request is sent from the client to the server and the 
> server has got the result and sent it back to the client. 
> The problem here is in the CorbaConduit we have a 
> CorbaMessage once I call OnMessage on the incomingObserver - 
> In the clientImpl in Cxf it creates a new message so I end up 
> with a CorbaMessage within a CorbaMessage which then contains 
> the MessageImpl. My first CorbaMessage had a destination etc 
> set which the new message doesn't so I loose all this 
> information I need.
> Is it possible to make the creation of the new Message optional ?
> thanks, Edell.

View raw message