Return-Path: Delivered-To: apmail-ws-axis-dev-archive@www.apache.org Received: (qmail 31504 invoked from network); 24 Nov 2003 15:55:10 -0000 Received: from daedalus.apache.org (HELO mail.apache.org) (208.185.179.12) by minotaur-2.apache.org with SMTP; 24 Nov 2003 15:55:10 -0000 Received: (qmail 42290 invoked by uid 500); 24 Nov 2003 15:54:59 -0000 Delivered-To: apmail-ws-axis-dev-archive@ws.apache.org Received: (qmail 42255 invoked by uid 500); 24 Nov 2003 15:54:58 -0000 Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm Precedence: bulk Reply-To: axis-dev@ws.apache.org list-help: list-unsubscribe: list-post: Delivered-To: mailing list axis-dev@ws.apache.org Received: (qmail 42188 invoked from network); 24 Nov 2003 15:54:58 -0000 Subject: RE: [wsif] contribution on SOAP over JMS part To: jmeritt@sonicsoftware.com Cc: axis-dev@ws.apache.org X-Mailer: Lotus Notes Release 5.0.6a January 17, 2001 Message-ID: From: ext-thierry.templier@ccf.com Date: Mon, 24 Nov 2003 16:46:01 +0100 X-MIMETrack: Serialize by Router on FR-SMTP-02/SERVERS/HSBC (Release 5.0.10 |March 22, 2002) at 24/11/2003 16:46:04 MIME-Version: 1.0 Content-type: text/plain; charset="us-ascii" X-Spam-Rating: daedalus.apache.org 1.6.2 0/1000/N X-Spam-Rating: minotaur-2.apache.org 1.6.2 0/1000/N Hello Jaime, > Thierry, > > I would be happy to help with the patch to the SimpleJMSListener/Worker. If > you want I can review the code and commit your patch. Thanks, because it's the first time I make a patch on an apache project! > There is no problem with the code you sent because it fully implements your > correlation strategy. The only issue is that the message_id->correlation_id > is not the only strategy that could be in use. Therefore I don't think > putting this specific implementation into the worker is appropriate, rather > I would like to discuss the other options with you and try to come up with a > generic way of supporting correlation strategy. Furthermore, this is not > only a problem in the JMS space, but is inherent in any asynchronous > transport so we may want to address it at a higher level. I really enjoy to discuss the generic way of supporting correlation with you too. I read some articles on WS-Policy and I now understand its concept. How will SimpleJMSWorker detect the correlation strategy of the sender of the message? Has something already been done out of the jms context? What about the different JMS supported messages ? Is it right to patch the code of the worker in order to do it ( extract message of different types of JMS messages )? > Thanks, > Jaime Thanks, Thierry Les informations contenues dans ce message sont confidentielles et peuvent constituer des informations privilegiees. Si vous n etes pas le destinataire de ce message, il vous est interdit de le copier, de le faire suivre, de le divulguer ou d en utiliser tout ou partie. Si vous avez recu ce message par erreur, merci de le supprimer de votre systeme, ainsi que toutes ses copies, et d en avertir immediatement l expediteur par message de retour. Il est impossible de garantir que les communications par messagerie electronique arrivent en temps utile, sont securisees ou denuees de toute erreur ou virus. En consequence, l expediteur n accepte aucune responsabilite du fait des erreurs ou omissions qui pourraient en resulter. --- ----------------------------------------------------- --- The information contained in this e-mail is confidential. It may also be legally privileged. If you are not the addressee you may not copy, forward, disclose or use any part of it. If you have received this message in error, please delete it and all copies from your system and notify the sender immediately by return e-mail. E-mail communications cannot be guaranteed to be timely secure, error or virus-free. The sender does not accept liability for any errors or omissions which arise as a result.