Re: Blueprint or DS or what to use?

I realise rereading my post that it may have been a little ambiguous as to which direction we have taken => we have decided that Declarative Services will be the best solution for us long term. -- View this message in context:

Re: Blueprint or DS or what to use?

If I might throw in another tech, which hasn't been talked of yet. Another possibility would be to take a look at CDI, we have pax-cdi which does a fair share of leveraging cdi stuff in osgi and afaik someone from IBM started to work on something to have cdi 2.0 be compatible to OSGi. Especially

Re: Blueprint or DS or what to use?

np > On 21 Mar 2016, at 09:25, Jean-Baptiste Onofré wrote: > > Hi Richard, > > Thanks again for your help, much appreciate ! > > Let me send a private e-mail to you (copy with people involved in the > decision in my company). > > Thanks ! > Regards > JB > > On

Re: Blueprint or DS or what to use?

Hi Richard, Thanks again for your help, much appreciate ! Let me send a private e-mail to you (copy with people involved in the decision in my company). Thanks ! Regards JB On 03/21/2016 10:20 AM, Richard Nicholson wrote: JB - As I directly offered to you during our discussion in 2015 -

Re: Blueprint or DS or what to use?

Hi Tim, On 21.03.2016 09:48, Timothy Ward wrote: Hi Christian, On 21 Mar 2016, at 08:27, Christian Schneider > wrote: Indeed it is difficult to predict where the OSGi community will go in the future. I’m not sure that I agree with

Re: Blueprint or DS or what to use?

JB - As I directly offered to you during our discussion in 2015 - if I can help in any way please let me know. Myself and other OSGi Board Members are more than happy to help any company that is considering joining the OSGi Alliance. Best Wishes. > On 21 Mar 2016, at 09:04, Jean-Baptiste

Re: Blueprint or DS or what to use?

Hi Tim, FYI, Guillaume was involved in the Blueprint specification (and he's OSGi Alliance member via RedHat if I remember well). Regards JB On 03/21/2016 09:48 AM, Timothy Ward wrote: Hi Christian, On 21 Mar 2016, at 08:27, Christian Schneider

Re: Blueprint or DS or what to use?

Hi Richard, we already had discussion with the OSGi Alliance. Christian and I asked if it would be possible to work on specifications "outside" of our company first, as OpenSource guys. It seems very difficult, so now, we are discussing internally with our company. Regards JB On 03/21/2016

Re: Blueprint or DS or what to use?

> On 21 Mar 2016, at 08:27, Christian Schneider wrote: > > Indeed it is difficult to predict where the OSGi community will go in the > future. No great mystery, no crystal ball need and easily addressable. Companies making profit out of the Karaf community (selling

Re: Blueprint or DS or what to use?

Hi Christian, > On 21 Mar 2016, at 08:27, Christian Schneider wrote: > > Indeed it is difficult to predict where the OSGi community will go in the > future. I’m not sure that I agree with this. OSGi RFPs and RFCs are publicly available at

Re: Blueprint or DS or what to use?

Indeed it is difficult to predict where the OSGi community will go in the future. For DS the situation is hopefully a little better today than at the time I did the comparison. - JPA can be solved today by using the Aries JPA and JPATemplate but it is not standardized. The upcoming spec

Re: Blueprint or DS or what to use?

Andreas you are crossing or about to cross a bridge we are crossing at the moment. We also have a SpringDM based application. It is 3+ years in production and so a change as large as moving away from SpringDM is very disruptive. For the most part we considered only Aries Blueprint vs DS. However

RE: Blueprint or DS or what to use?

We use Blueprint mainly to have a code which makes use of services but without dealing with OSGi or annotations (as far as possible => few wappers). As long with the maven-bundle-plugin it is a kind of magic. I would say Blueprint+Maven+Karaf makes things really easy. I would suggest to make a

Re: Blueprint or DS or what to use?

No, there aren't any docs at the moment, and it has not been much used yet. I haven't had any time to write a karaf feature for it yet ... The blueprint-spring bundle allows you to use the standard spring namespace along with spring custom namespaces from blueprint applications. The

Re: Blueprint or DS or what to use?

I personally use Blueprint cause of: 1. common spring-like xml style of DI 2. prototype scopes 3. creating and describing internal skeleton of bundle in one file 4. CXF integration -- View this message in context:

Re: Blueprint or DS or what to use?

Fwiw, you need to use the following bundles (blueprint-core, blueprint-spring, blueprint-spring-extender) which are being released: https://repository.apache.org/content/repositories/orgapachearies-1061 2016-03-18 17:08 GMT+01:00 akuhtz : > Hello, > > Thank you for

Blueprint or DS or what to use?

Hello, I've an application running with spring-dm and because spring-dm is no longer developed I'm looking for a replacement. Now I'm confused because there was a shift in karaf (core) from blueprint to DS and today I saw a post on the dev list, saying that DS does not support as much as

Re: Blueprint or DS or what to use?

I have a comparison in my DS tutorial. http://www.liquid-reality.de/display/liquid/2015/06/30/Apache+Karaf+Tutorial+part+10+-+Declarative+services The main two things missing in DS are the namespaces and the interceptors. In karaf internally we would not need those. In a typical user

Re: Blueprint or DS or what to use?

On 18.03.2016 13:07, Charlie Mordant wrote: Let introduce an other player: Pax-CDI! It is fully annotation based and a well known JavaEE standard with some additional annotations to deal with OSGi services. I really prefer this way for development. I'm used to deal with these 3 technologies

Re: Blueprint or DS or what to use?

Can you point me to any documentation on this? I found a thread on the aries-dev but that's about it. When we abandoned Gemini we lost some of the functionality and would be interested in trying this out.

Re: Blueprint or DS or what to use?

Depends upon your application, and what you want to do. Each has their benefits, and detractions. Personally I tend to use Blueprint for small wiring setups (say an AMQ connection factory, and a Camel Context). On Fri, Mar 18, 2016 at 7:54 AM, akuhtz wrote: > Hello, >

Re: Blueprint or DS or what to use?

Let introduce an other player: Pax-CDI! It is fully annotation based and a well known JavaEE standard with some additional annotations to deal with OSGi services. I really prefer this way for development. I'm used to deal with these 3 technologies and here are the case where I use one or

Re: Blueprint or DS or what to use?

Hello, Thank you for all the helpful answers and pointers! I'll try to go first with the solution proposed by Guillaume and see if I get it working. Regards, Andreas 2016-03-18 14:10 GMT+01:00 CLEMENT Jean-Philippe [via Karaf] < ml-node+s922171n4045858...@n3.nabble.com>: > We use Blueprint

Re: Blueprint or DS or what to use?

Hi, From an OSGi standards perspective it’s worth pointing out that the Blueprint specification has not been touched since it was first released in OSGi 4.2. There are a few proposed extension RFCs for Blueprint, but none have seen much activity in five years or more. Declarative Services,