I agree that ESB and WSIF are not the same but one could
easily ask
himself : Do I need a full scale solution like ESB or do I
need only a
client-side connecting facility ?
WSIF gives the opportunity to use a service repository (your
code)
without compromising your calling code (your client).
ESB offers this feature over SOAP (almost all of them) and
allow you to
deploy whatever service you want behind the ESB access. And
to do a lot
more ! security, transformation, monitoring, etc.
So one should ask himself do I ONLY need to make my client
"service
implementation independent" ? if the answer is
definitely yes then WSIF
is eligible.
If you have doubts or if you know you must go farther, go
look for a
nice ESB and be prepare to set up a full grade server
solution
best,
Cyril
Aleksander Slominski a écrit :
> Andre P. wrote:
>
>> Hello everyone.
>>
>> Will ESB (or have it already) embody the WSIF
functionalities?
>>
>> Why should I use WSIF instead of an ESB (or
vice-versa)?
>>
> i think it completely depend on use case and comparing
ESB and WSIF is a
> bit like oranges and apples - WSIF is just a client
side library - ESBs
> typically imply whole system - that is my .01c
>
> best,
>
> alek
>
>
--
*Cyril Rognon*
Responsable Capitalisation
+33 1 55 93 36 87
+33 6 08 89 16 86
crognon sqli.com <mailto:sjobs sqli.com>
268, avenue du Président Wilson 93210 LA PLAINE-SAINT-DENIS
Std : +33 1 55 93 26 00 - Fax : +33 1 55 93 26 01
*"SQLI Consulting, l'expert du conseil IT"*
www.sqli.com <http://www.sqli.com>
/-----------------------------------------------------------
-----------------------
Ce message et toutes les pièces jointes (ci-après le
"message") sont
confidentiels et établis à l'intention exclusive de ses
destinataires.
Toute utilisation ou diffusion non autorisée est interdite.
Tout message
électronique est susceptible d'altération.
------------------------------------------------------------
----------------------
/
|