Stefan Tilkov wrote:
> On Aug 24, 2006, at 4:04 AM, Gregg Wonderly wrote:
>>Stefan Tilkov wrote:
>>>(1) select an ESB that supports all of these
>>>(2) for each technology, select some product that service-enables it
>>
>>What would you view as being "service-enabled"?
>
> Well -- whatever you want to. Seriously, which particular sets of
> protocols and standards you standardize does not really matter for
> this particular discussion IMO. I'm a fan of wire standards as
> opposed to API standards, but even that is not that relevant in this
> context. (And the usual way to "service-enable" something is, in my
> experience, to create a wrapper application, not use an off-the-shelf
> product.)
This is what I was trying to find. So you're that wrapping for compatibility
at
the application (so that it doesn't spill its dependencies outside of that
domain on its legacy tecnologies perhaps?), rather than connecting for
interoptabilty to another application (such as an ESB) is the better plan?
Gregg Wonderly
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/
