cxf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From liucong <liucon...@gmail.com>
Subject Re: request-response patterns.
Date Sun, 26 Jul 2009 14:40:27 GMT
Hi,
If the client doesn't configure something about the CorrelationID, I'll
use MessageId pattern.

The current implement use CorrelationId by default. So I think I should
change the rule. I use MessageId pattern by default.


Christian Schneider wrote:
> Hi Liu,
>
> the current code uses the MessageId Patternif the Correlation Id is empty.
> It sends the response to the specified replyTo queue. For CorrelationId
> Pattern it would always use the same queue.
>
> Greetings
>
> Christian
>
> liucong schrieb:
>   
>> Hi,
>>
>> Some information about JMS Correlation ID patten and Message ID pattern
>> on request-response patterns
>> (http://edocs.bea.com/alsb/docs25/interopjms/MsgIDPatternforJMS.html).
>>
>> By digging into the code about jms-transport, I know the current
>> jms-transport uses the Correlation ID Pattern. But the SOAP/JMS
>> specification uses Message ID Pattern.
>>
>> What should I do?
>> 1. To keep Correlation ID Pattern. But it is not compatible with the
>> specification.
>> 2. To use Message ID Pattern. I see some code which use spring-jms, I
>> can't get the id of the message which is sent by spring-jms. I don't
>> know how to get the message id which is used to correlated the response
>> message.
>>
>> Thank you for your sugguest in advance.
>>
>> liu
>>
>>   
>>     
>
>
>   


Mime
  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message