Mailing-List: contact dev-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@camel.apache.org
From: "Ranx" <ranx@enjekt.org>
To: <dev@camel.apache.org>
Subject: CDI?
Date: Wed, 12 Apr 2017 13:52:35 -0500
Message-ID: <078401d2b3bd$f3a6c730$daf45590$@enjekt.org>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_NextPart_000_0785_01D2B394.0AD10D50"
Thread-Index: AdKzvYlLES6szTdkRAWv9w3yeBGUVw==
Content-Language: en-us
archived-at: Wed, 12 Apr 2017 18:52:50 -0000

------=_NextPart_000_0785_01D2B394.0AD10D50
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

I'm not quite sure I follow the comments on this issue.

 
https://issues.apache.org/jira/browse/CAMEL-11029

 
According to the Camel documentation there seems to be a lot of work being
done on the Camel CDI in 2.18 so how can it simultaneously be deprecated? 

 
http://camel.apache.org/cdi.html

 
It's possible I'm misunderstanding this somehow and that the deprecation is
due to a difference in Camel and the later versions of Karaf? Or does this
have to do with Guillaume's new PAX DS implementation of CDI?

 
Thanks for any clarification.

 
Ranx


------=_NextPart_000_0785_01D2B394.0AD10D50--