> My issue with the Java platform is that it requires a different API for
It doesn't _require_ it - it's just that the vendors involved saw fit to
architect it that way.
One could build a layer over the top - in fact, some have (e.g. Mule).
> 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")?
>
Perhaps they have different design centres?
Doesn't this come down to the age old "One size fits all vs something
more custom" argument?
Each approach has it's merits and each has it's faults and which fits
with what you're doing changes day by day as your requirements/systems
change.
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.
