Eugen,

Just FYI, you don't actually have to wait. As Peter aluded, there are several implementations available now. The spec appears to be undergoing change but if you want to get started and are willing to adapt when the spec settles knock yourself out. I have used the ECF remote messaging to great success in a few cases. You can do the current distributed services draft spec style or the native ECF style. Plug in different transports, ...

Jeff

Eugen Reiswich wrote:
Thanks Peter,

this is exactly what I wanted to know! I will wait for RFC 119...

Kind regards
Eugen

Am May 20, 2009 um 17:02  schrieb Peter Kriens:

The upcoming R4.2 will provide a Remote Services section that allows you to decouple bundles from the underlying distribution provider. This means that the only dependency in your code you have on the distribution provider is a number of properties + the OSGi service API. These properties should be settable by configuration management. The intention is that you can switch distribution provider without changing your app bundles, only have to change the properties. We are currently working very hard to create the spec based on the RFC 119 for this area and things are still a bit in flux so the RFC 119 is currently unfortunately a bit stale.

ECF, CXF, and others are implementing this specification as distribution providers.

Kind regards,

    Peter Kriens





On 19 mei 2009, at 20:05, 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.

Regards,
Eugen
_______________________________________________
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

_______________________________________________
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

Reply via email to