axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ext-thierry.templ...@ccf.com
Subject RE: [wsif] contribution on SOAP over JMS part
Date Fri, 21 Nov 2003 09:20:33 GMT

Hi Jaime,

> The easiest thing to do (from my perspective) is to modify the
> SimpleJMSListener/Worker to accept TextMessage as well as BytesMessage
> instances.  That would allow it to interact with WSIF clients as well as
> Axis ones.

I think too that it could be great... Would you want help to do this?

> The correlation id issue:
>
> There are many ways of correlating messages including but not limited to the
> following:
>
> 1) Per-request response destinations (the correlator is the destination you
> receive it from)
> 2) Put the message id into the responses correlation id (very common)
> 3) Correlation at the app level in the message content (also very common)
>
> Axis clients use option 1 in the near term (this is not appropriate for a
> long term solution).  I don't think that adding the correlation code below
> (option 2) to the SimpleJMSWorker is appropriate.

Is it possible to implement option 2 in the SOAP over JMS? What is the
problem with the code I send you?
According to your message, I think that code in the SimpleJMSWorker isn't
appropriate because it isn't very evolutive if you want to implement the
option 3 in the future. Is it right?

> Due to the multi-paradigm nature of correlation I would suggest a strategy
> pattern on both the client and server to handle correlation.  Correlation
> strategy would be a part of the contract that the web service has with the
> client (I could envision WS-Policy assertions in the WSDL or something like
> that).  This way we could use a WS-* implementation for correlation, a JMS
> id based approach, etc.

I don't know WS-Policy specification. So I get informations about it and
its principles in order to discuss with you of the option 3.

> Thoughts?
> Jaime

Thanks for your answer!
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.


Mime
View raw message