> products (XML gateways, SOA management systems, enterprise systems
> management systems, ESBs, platforms, etc) don't know how to use it
> unless the vendors negotiate directly with Systinet to learn the
> semantics of the API.
One has to accept that a significant purches with those vendors today
is a worthwhile cost. I think the debate is about whether an
investment is the right thing to make or if time, people, and money
are best spent elsewhere. Personally I would not make a significant
decision today based on what those vendors are providing, it's just
way premature IMO.
Of course, the XML gateways, at least the ones I have looked at,
support "just HTTP" and things non-WS-*. So do other infrastructure
components.
> Meanwhile, vendors like AmberPoint, Actional, Sonic ESB, Reactivity,
> CA, HP, SOA Software, etc, can all implement generic registry
> integration functionality based on the UDDI protocol that seamlessly
> interoperates with Systinet 2, Infravio X-Registry, Software AG
> CentraSite, Sun Registry, Flashline, etc, etc.
If that floats your boat, then by all means go sailing.
-Patrick
SPONSORED LINKS
| Computer software | Computer aided design software | Computer job |
| Soa | Service-oriented architecture |
YAHOO! GROUPS LINKS
- Visit your group "service-orientated-architecture" on the web.
- To unsubscribe from this group, send an email to:
[EMAIL PROTECTED]
- Your use of Yahoo! Groups is subject to the Yahoo! Terms of Service.
