>> My issue with the Java platform is that it requires a different API for
>> 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.
>
:)
It's in the interests of the vendors to have it that way and it appears
we've dumbed down IT staff enough now so there's no push back from
clients to prevent it. Couple that with the fact that the "management"
are making technical decisions based on little knowledge or experience
(and they don't talk/listen to their IT staff) and I think we're doomed
to see this repeating.
I'd wager that we'll see exactly the same behaviour in the more "hot"
technologies in future years.
Sigh,
Dan.
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.
