Millies, Sebastian wrote:
thanks for the quote.
Do you think this decision by OSOA well-motivated? After all, e. g. OSGi
does not
make this restriction, and OSGi services are also coarse grained and
loosely coupled.
-- Sebastian
Sebastian,
In a word: "yes" - ie it is well motivated.
WSDL does not permit use of overloaded method interfaces - the use of Web services is a primary use
case for remotable services, so this is a pretty strong motivation on its own for SCA.
Going deeper, there is a reason that WSDL has this restriction - and that has to do with what can be
supported by varieties of languages that might form implementations of clients and/or services.
Some langauges can't deal with method/operation overloading. SCA is intended to be implementation
language neutral, so following this restriction makes a lot of sense, as it does for Web services.
OSGi may very well run into trouble by permitting overloading in the remotable service case - I
tried to convince them of this, but they are primarily motivated by the Java usecase, for which
method overloading works. That does not mean that you can then choose to take an interface using
method overloading and use it as a Web service interface. Caveat emptor...
Yours, Mike.
