Can't we use WS-Addressing to do this? Request Message ID = Relates to ID in response right?
Samisa... Ruwan Linton wrote: > Hi Basher, > > You should be adding a UUID for the property with a given Key... and it > should be the same value for the response as well, and since it is a > UUID no tow different requests have the same value for the property. > This way you can correlate the request and the response. > > Thanks, > Ruwan > > Kattubadi Basher Ahamed wrote: > >> Ruwan, >> Assume we client1 and client2 sends request to ESB, I will add property in >> message context or in header in request flow before sending to queue. >> If I receive response first for the client2-response instead of >> client1-response.how I need to correlate which response message need to set >> which request property. >> >> >> thanks >> >> >> -----Original Message----- >> From: [email protected] [mailto:[email protected]] >> On Behalf Of Ruwan Linton >> Sent: Tuesday, March 31, 2009 8:52 AM >> To: [email protected] >> Subject: Re: [esb-java-dev] Logging >> >> Hi Basher, >> >> I think usage of the message id for this purpose is not the correct approach >> for this scenario. Assuming that this queue is an internal Java queue which >> stores the message context object you could use a property with a given name >> to associate the request and the response, so in the response flow these >> properties will be copied to the response. >> >> If you are storing these messages as SOAP or XML messages in a JMS queue or >> any other external queue I propose you to use a custom SOAP header to keep >> the information about the request / response association. In this particular >> case you will need to add the value for the response message before >> reporting to the queue, well same with the request I guess. You could still >> use a property to correlate the request and the response in the synapse flow. >> >> Thanks, >> Ruwan >> >> Kattubadi Basher Ahamed wrote: >> >> >>> HI, >>> I am designing Logging frame work in ESB. >>> My requirement is from ESB I will send request and reply to one Queue, and >>> another flow called audit flow picks the request and response from that >>> Queue for particular client request/response and merge together and put >>> into Audit queue. >>> For synchronous call I can provide same message id for request and reply >>> and audit flow can picks the message from the queue with similar messageid >>> messages and merge together. >>> In case of Asynchronous message how we will maintain similar messageid for >>> both request and reply. >>> >>> Or is there any suggestion to handle this or any other design you >>> propose. >>> >>> Please reply . >>> >>> Thanks in advance >>> Basher >>> _______________________________________________ >>> Esb-java-dev mailing list >>> [email protected] >>> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev >>> >>> >>> >>> >> -- >> Ruwan Linton >> Senior Software Engineer & Product Manager; WSO2 ESB; http://wso2.org/esb >> WSO2 Inc.; http://wso2.org >> email: [email protected]; cell: +94 77 341 3097 >> blog: http://ruwansblog.blogspot.com >> >> >> _______________________________________________ >> Esb-java-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev >> >> _______________________________________________ >> Esb-java-dev mailing list >> [email protected] >> https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev >> >> >> > > > > ------------------------------------------------------------------------ > > > No virus found in this incoming message. > Checked by AVG - www.avg.com > Version: 8.5.285 / Virus Database: 270.11.34/2032 - Release Date: 03/31/09 > 06:02:00 > > _______________________________________________ Esb-java-dev mailing list [email protected] https://wso2.org/cgi-bin/mailman/listinfo/esb-java-dev
