> Yes, I wouldn't say that by definition the use of static languages
> and binary serialized XML prohibits loose coupling.
There are two issues here Eric. One is whether in a Java only service and
client environment, whether Interface based programming using the RMI
programming model is any more binding than any other description of the service
interface. The second is whether you can also use Java to make use of other
invocation and transfer technologies to decouple your Java based systems from
the Java platform to allow them to interact with other systems.
I believe that the interface based programming model of Java is only as binding
as you make it. You have to make smart decisions about the level of
abstractions that you use in your interface definitions. In addition, mobile
code allows you FIX your data and service model by maintaining a particular
interface at the client. A smart proxy implementation allows the service
interface to change. Interface based programming also allows you to extend your
service definition in a backward compatible way through subclassing.
In the second case, Java (and Jini's JERI as I've repeatedly stated) provide
ample opportunities for you to use standards based invocation and transfer
technologies to communicate with a wide range of systems.
Gregg Wonderly
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.
