Hi Scott,
ECF is definitely one approach (and it does it really good) but since
it is not the only one remote framework I'm looking for a way to
decouple my bundles from any technology as much as possible. The goal
is to be able to switch from ECF to Riena or RMI or some other
technology with a minimal effort.
Regards,
Eugen
Am May 19, 2009 um 20:31 schrieb Scott Lewis:
Hi Eugen,
Eugen Reiswich wrote:
Hi,
we are developing a client/server application with osgi. Say I have
three bundles:
1. client
2. common (includes the service interface and domain value objects)
3. server (includes the service implementation)
We've started to develop our application with the remote technology
RMI but switched now to Riena. As it was really a pain to remove
all RMI dependencies from our code (e.g. all RemoteExceptions) I
wonder if there is a best practise approach how to achieve a loose
coupling of a specific remote technology in our osgi bundles
without using tons of wrappers.
Well, I wouldn't call it a best practice at this point, but using an
abstract remoting API like the ECF remoteservices API results in
exactly this (separation of specific remote technology from the
client code). Having such a loose coupling between a specific
remoting technology and client code was part of the intention of
creating the abstraction.
Scott
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
_______________________________________________
OSGi Developer Mail List
osgi-dev@mail.osgi.org
https://mail.osgi.org/mailman/listinfo/osgi-dev
