Re: CDI?

Weird, I didn't see this last year after you posted it. I don't know why. I was up here reading on the latest as I'm going to be doing some prototyping with Fuse 7 and wanted to see what latest best practices are and where CDI is after the February release date. I probably should write a

Re: CDI?

On 15.08.2017 16:06, r...@enjekt.org wrote: Christian, I've also seen a lot of people using Processors/Exchanges which unnecessarily couples their cod to the Camel framework. Unfortunately the Camel in Action book doesn't get around to advising against that practice until your well over 100

Re: CDI?

I'm not quite sure I grok this. I've used both Blueprint and DS. I've also used CDI but it isn't quite ready for primetime. But CDI permits exporting services, referencing services, and wiring bundle internals with injection annotations. It greatly simplifies testing. So I'm not quite sure

Re: CDI?

I agree. Not using services in OSGi is a bad idea. Services allow you to keep your bundles loosely coupled. You should also try to only use standard java types in your service interfaces. I have seen some cases where people share camel routes between bundles or use camel classes in service

Re: CDI?

It is certainly worth to try. I would be very interested in your experience with the current state of CDI support. Christian 2017-08-09 17:20 GMT+02:00 : > Matt, > > This is an exchange between Christian and Guillaume from couple of months > back when I was asking about this.

Re: CDI?

What I found odd about the Camel comment that Claus made is that Guillaume just put in the CDI annotations for service export and reference last year. Initially he did it with Blueprint but swapped it out with DS. I prefer working with CDI as there is a lot of testing I can do in Camel that

Re: CDI?

Hi, The OSGi CDI spec was never approved as the champion pushing the spec withdrew. At the time People here at OPS4j worked on a CDI implementation which should follow that spec. That's Pax CDI, but as the spec was never approved that's basically it. Though it's functional working. Besides, the

Re: CDI?

I'm not so sure about deprecated, but DS is the only dependency injection standard in OSGi that respects the dynamic nature of services. CDI, blueprint, etc., all have to rely on hacky proxies to emulate support while adding nonstandard extensions at times. On 7 August 2017 at 17:02,