RE: WSIF or ESB ?

Folks,

Check the JIRA, we have incoming support for Axis2 

-- dims

On 2/13/07, Gregory Prokter <proktercomcast.net> wrote:
>
>
> Let me  add my thoughts to the discussion as I have
come across the same question.   First, there is cost. 
Commercial ESB is very expensive, whereas WSIF is  free. 
But most IT organizations I know, have already purchased
ESB,  so it's a mute point.  Second, ESB as pointed out
below is so much more  functionality (repository, client
access over any protocol,  monitoring, security, 
asynchronous call outs to other services in the  pipe, etc.)
than WSIF that it is indeed as Alek pointed out like
comparing  Apples to Oranges.
>
> So, if  you have a small nail (client access to a
service independent of protocol)  of course bringing a HUGE
hammer like ESB will do the job.  But then, be  careful with
your fingers!
>
> Best regards,
>
> Gregory Prokter
>
>
> "Things should be as simple as possible, but not 
any simpler" - Albert Einstein
>
>
>
>
>
>
> This e-mail transmission contains information that  is
confidential and may be privileged.  It is intended only for
the  addressee(s) named above.  If you receive this e-mail
in error, please do  not read, copy or disseminate it in any
manner.  If you are not the  intended recipient, any
disclosure, copying, distribution or use of the contents  of
this information is prohibited.  Please reply to the message
immediately  by informing the sender that the message was
misdirected.  After replying,  please erase it from your
computer system.  Your assistance in correcting  this error
will be appreciated.
>
>
> -----Original Message-----
> From: Cyril Rognon    [mailto:cyril.rognonsysdeo.fr]
> Sent: Tuesday, February 13, 2007    2:20 AM
> To: wsif-userws.apache.org
> Subject: Re:    [xgws-user] WSIF or ESB ?
>
> 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
> crognonsqli.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
>
>
------------------------------------------------------------
----------------------
> 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.
>
------------------------------------------------------------
----------------------
>



-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for
Web Services Developers

------------------------------------------------------------
---------
To unsubscribe, e-mail: wsif-user-unsubscribews.apache.org
For additional commands, e-mail: wsif-user-helpws.apache.org

Gregory Prokter wrote:
> Let me add my thoughts to the discussion as I have come
across the
> same question.  First, there is cost.  Commercial ESB
is very
> expensive, whereas WSIF is free.  But most IT
organizations I know,
> have already purchased ESB, so it's a mute point. 

Just wanted to mention that there are several open source
ESB solutions
emerging. here are some examples:

Open ESB: <https://open-esb.d
ev.java.net/>
Mule: <http://mule.mulesource.org/wiki/display/MULE/Home>

> Second, ESB as pointed out below is so much more
functionality
> (repository, client access over any protocol,
monitoring, security,
>  asynchronous call outs to other services in the pipe,
etc.) than WSIF
> that it is indeed as Alek pointed out like comparing
Apples to Oranges.
>  
> So, if you have a small nail (client access to a
service independent
> of protocol) of course bringing a HUGE hammer like ESB
will do the
> job.  But then, be careful with your fingers!

Good point. My experience is that projects often start out
needing small
nails and timber but then grow to need bigger timber, nails,
hammer and
power tools. Even the pros need to be careful with such
power tools 
-- 
Regards,
Farrukh

Web: http://www.wellfleet
software.com



------------------------------------------------------------
---------
To unsubscribe, e-mail: wsif-user-unsubscribews.apache.org
For additional commands, e-mail: wsif-user-helpws.apache.org