Hi Freeman, Thanks for your reply.
> I don't think CXF can support one request with multiple response. Could you please help me to understand why CXF cannot support this feature? JMS transport is an example, I also want to use a long-live transport (local transport, jms tcp) to send multiple response message, ( e.g. I send request to a cxf webservice to ask service sending some data to the client every minute. ) Regarding the example *client creating a callback object by passing an EndpointReferenceType to the server*, it sounds interesting, could you please point out the example name so that I can check it? thanks again. David On Tue, Apr 12, 2011 at 10:06 AM, Freeman Fang <[email protected]>wrote: > Hi, > > I don't think CXF can support one request with multiple response. > However, per your requirement, asides from the normal response, you can > always send any message to the JMS queue with JMS api in your service > implementations. > Another option is that you can use callback, which means client creating a > callback object by passing an EndpointReferenceType to the server, then the > server can act as a client and callback for any times, we have callback > examples shipped with kit, you may need take a look. > > Freeman > > On 2011-4-12, at 上午8:57, Yinwei David Liu wrote: > > Hi cxf-users, >> >> I would like to know what you think if CXF can support multiple response >> in its service? >> >> Currently, one CXF service can only return one Response message for each >> Request. However, there are some use case that we want one request have >> multiple response messages. E.g. my service gets a jms request from a >> client, and then, it will reply 3 response messages to a JMS queue. >> >> Is there any consideration to support multiple response message for this >> kind of use case? >> >> David >> > > --------------------------------------------- > Freeman Fang > > FuseSource > Email:[email protected] > Web: fusesource.com > Twitter: freemanfang > Blog: http://freemanfang.blogspot.com > Connect at CamelOne May 24-26 > The Open Source Integration Conference > > > > > > > > >
