> >I tend to look at SOA infrastructure in four categories:
> >1. Protocol and policy focused offerings (ESB, Service Fabric,
AON)
> >2. WSDL based technical services (data services, collaboration
> >services, etc.)
> >3. The cross-cutting technical concerns (security, governance,
> >managability)
> >4. Lifecycle tooling (architecture, design, code, test, etc.)
>
> There's no reason an ESB shouldn't offer all of these things. In
fact,
> I would say that any ESB offering that doesn't, is lacking.
Then, I must conclude that you believe that ESB = ALL Service
Oriented Infrastructure. Hence, I must also conclude that you
believe that the Sonic Suite is "lacking".
I'm quite confident that I am misunderstanding your point. Can you
please clarify?
Jeff
Yahoo! Groups Links
<*> To visit your group on the web, go to:
http://groups.yahoo.com/group/service-orientated-architecture/
<*> To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
<*> Your use of Yahoo! Groups is subject to:
http://docs.yahoo.com/info/terms/
