Re: [osgi-dev] OSGifying an existing application

Thanks Scott. Cheers, Peter. Sent from my Samsung device.     Include original message Original message From: Scott Lewis <sle...@composent.com> Sent: 27/02/2017 05:09:27 am To: osgi-dev@mail.osgi.org Subject: Re: [osgi-dev] OSGifying an existing application On 2/21/2017 3

Re: [osgi-dev] OSGifying an existing application

On 2/21/2017 3:29 AM, Peter wrote: Christian, I will investigate it, if I can navigate a path through the serialization issues. It is actually looking quite positive. For your info: ECF's impl of RS/RSA has three APIs of use for creating distribution and discovery providers: 1) A

Re: [osgi-dev] OSGifying an existing application

ges and >>>versions) via the Jini service registrar, services that are not >>>api compatible will be filtered out. >>> >>>The server / service remains responsible for maintaining >>>compatibility. >>> >>> Discovery is dynamic. >

Re: [osgi-dev] OSGifying an existing application

osgi-dev@mail.osgi.org <mailto:osgi-dev@mail.osgi.org>> Subject: Re: [osgi-dev] OSGifying an existing application The problem is that in all distributed I’ve been involved in there were rolling updates. This implies that you cannot guarantee that each server runs the same

Re: [osgi-dev] OSGifying an existing application

> Peter. > > Sent from my Samsung device. > > Original message > From: Peter Kriens <peter.kri...@aqute.biz <mailto:peter.kri...@aqute.biz>> > Sent: 21/02/2017 12:24:39 am > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org > <mailto:osgi-dev@mail

Re: [osgi-dev] OSGifying an existing application

Regards, > > Peter. > > Sent from my Samsung device. > > Original message > From: Peter Kriens <peter.kri...@aqute.biz> > Sent: 21/02/2017 12:24:39 am > To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> > Subject: Re: [osgi-dev] OSGifying an e

Re: [osgi-dev] OSGifying an existing application

Samsung device.     Include original message Original message From: Peter Kriens <peter.kri...@aqute.biz> Sent: 21/02/2017 03:49:01 am To: OSGi Developer Mail List <osgi-dev@mail.osgi.org> Subject: Re: [osgi-dev] OSGifying an existing application It is wonderful to not be complete

Re: [osgi-dev] OSGifying an existing application

e: [osgi-dev] OSGifying an existing application The problem is that in all distributed I’ve been involved in there were rolling updates. This implies that you cannot guarantee that each server runs the same bundle. And clusters that do not do rolling updates seem kind of useless because they intr

Re: [osgi-dev] OSGifying an existing application

It is wonderful to not be completely shut down this time. A few years ago making the kind of comments I am making now and I would have been condescendingly looked at, while you saw people thinking that I probably tried to hide a deficiency in OSGi. :-) This is a fundamental computing problem.

Re: [osgi-dev] OSGifying an existing application

I was thinking about how ActiveMQ added extra security around serialization by forcing you to configure which packages it allows for serialization. That struck me as similar to import-/export-package and made me think that if you're using serialization like this, you should at the very least be

Re: [osgi-dev] OSGifying an existing application

The problem is that in all distributed I’ve been involved in there were rolling updates. This implies that you cannot guarantee that each server runs the same bundle. And clusters that do not do rolling updates seem kind of useless because they introduce a huge failure point. So I have a hard

Re: [osgi-dev] OSGifying an existing application

Thanks Pete, good to hear from you again, I must admit it's been too long. We last spoke when I was refactoring a class dependency tool to use ASM instead of the jdk's tools.jar. You once asked, how do you find a dependency for calls to Class.forName? The reasons you've stated are also why

Re: [osgi-dev] OSGifying an existing application

Hi Peter, Thanks for this. I have a comment to make about what you write, but out of respect for the original poster, I will create a new thread. See you in a few seconds. Cheers, =David > On Feb 20, 2017, at 5:38 PM, Peter Kriens wrote: > > After working in

Re: [osgi-dev] OSGifying an existing application

After working in this area for too many years I’ve come to the conclusion that objects cannot be really transferred to other systems in a reliable way, only self typed data can. JPA, RMI, and many other systems promise heaven to the programmer that they can use their objects local and remote

[osgi-dev] OSGifying an existing application

Hello, I'm currently working on converting an existing application to OSGi. This application has a network service architecture based on java interfaces. I've broken the application into modules, using a Maven build, which uses bnd and bndtools to create bundle manifests. Some of these