>each type of middleware/communication pattern. Why does the platform
need
>so many APIs/plug-in patterns for communications: JAX-WS, JMS, JBI,
JCA,
>etc? How about taking an approach more like Microsoft's Windows
>Communication Foundation (aka "Indigo")?
You mean, why is the Java world (vendors and 'community') so fractured
and foolish and unable to see the ARY (Always Repeat Yourself) and KICS
(Keep It Complicated (and) Stupid) models they're been not only
following but actively embracing and promoting for the past decade are
serious, severe and foundational problems of their own making and which
are, all too likely, fatal ones at that?
Gee. I dunno.
"If you can't be a good example, then you'll just have to serve as a
horrible warning."
[Good thing the Web Services world didn't pay heed or who knows where
the industry might have wound up...]
- Howard
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.
