[news.eclipse.technology.riena] Re: R-OSGi

[Christian Campo <christian.campo@xxxxxxxxxxxx>]

Hi Scott,

I think its good news for everyone.

As we discussed in the past, Riena's own communication library was created as "Noyta" 6-9 month ago.

I believe that Riena has to follow the path of supporting multiple libs for a whole list of various functionalities.

Just as an example we like to support different libs for Persistence (EclipseLink, Hibernate,....)
or for Software Update (P2, Maynstall,.....) or for Communication (ECF, OSGi-R, Riena communication,....) or
Deployment Container on the Server (Jetty, Tomcat, WAS, ....)

And there are many other areas where multiple implementations exist.

Its the choice of the implementation of a Riena based application what lib or bundle he picks. Its not
our choice as the supplier of the platform.

Since ECF now also supports transparent remote OSGi services, no dependency in the business code should or must exist
for any of these infrastructure bundles. Instantiating OSGi service could and should be done in seperate
config bundle and not in the business component itself.

So I say it again, using ECF in Riena is definitely a good choice, however a choice requires a list to choose from.

Once we get to our first version, I will contact you again to see how we can integrate our security requirements into ECF.

Please keep me posted on the progress

- christian


Scott Lewis schrieb:
> FYI,
>
> Jan Rellermeyer, the author of r-OSGi has joined the ECF team as a 
> contributor, and is in the process of implementing the ECF remote 
> services API with r-OSGI.  That is, he is using r-OSGi to implement the 
> ECF remote services API: 
> http://wiki.eclipse.org/index.php/ECF_API_Docs#Remote_Services_API
>
> We've also finished an update to the ECF discovery API:
> http://wiki.eclipse.org/index.php/ECF_API_Docs#Discovery_API
>
> Jan has also committed his SLP implementation and an ECF discovery API 
> implementation has been created out of it.
>
> The purpose of the ECF discovery and remote services API is to provide a 
> transport-independent access to remote OSGi services, with proxies, as 
> well as asynch invocation, one-ways, and future style of remote invocation.
>
> I hope the Riena team doesn't go to the trouble of creating a 
> transport/communications independent discovery and/or remote services 
> APIs...since it would be more efficient and community-friendly to use 
> and/or build upon, improve and extend the ECF APIs in these two areas.
>
> Scott
>
>
> Christian Campo wrote:
> > Hello Bryan,
> >
> > thanks for your interest in Riena. Yes we have looked at R-OSGI as 
> > well as ECF and other communication APIs. Quit a number of people also 
> > explained to us that they have written their own remoting option for 
> > OSGi so there is a requirment
> > for remoting and a number of APIs.
> >
> > Riena needs communication to create the distributed application model 
> > and it will not limit its user to a single
> > communication framework. However Riena has a number of requirements 
> > that need to be fullfilled by such a communication
> > lib such as security. Using HTTP/HTTPs is one, passing session ids for 
> > your logged-in identiy is another.
> >
> > We are currently in the process of creating a list of these 
> > requirments and implementing them for the first communication 
> > framework (which will be part of Riena itself). The plan is to then 
> > later implement adapters or
> > extensions for other frameworks. That can be done by ourselves or by 
> > interested parties.
> >
> > I currently don't see why R-OSGi could not be enabled to run Riena.
> >
> > BTW the communication that will be part of Riena is already described 
> > here: http://eclipse.compeople.eu/wiki/index.php/Nyota:Main. However 
> > it will no longer be called Nyota but rather
> > Riena communication.
> >
> > If you have more questions, please let me know.....
> >
> > christian campo
> >
> >
> > Bryan Hunt schrieb:
> > > Alexander,
> > >
> > > I'm quite interested in Riena as my application is already an RCP 
> > > client / OSGi server.  Have you looked at R-OSGi  
> > > http://r-osgi.sourceforge.net/ ?  I've been using it (without jslp) 
> > > for months and it just works.
> > >
> > > Bryan