svn commit: r980016 - in /websites/production/camel/content: cache/main.pageCache cdi.html

[buildbot]

Author: buildbot
Date: Wed Feb 10 11:18:54 2016
New Revision: 980016

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/cdi.html

Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.

Modified: websites/production/camel/content/cdi.html
==============================================================================
--- websites/production/camel/content/cdi.html (original)
+++ websites/production/camel/content/cdi.html Wed Feb 10 11:18:54 2016
@@ -410,7 +410,7 @@ void observeCdiEvents(@Observes @Context
 <script class="brush: text; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[cdi-event://PayloadType&lt;T1,...,Tn&gt;[?qualifiers=QualifierType1[,...[,QualifierTypeN]...]]]]></script>
 </div></div><p>With the authority&#160;<code>PayloadType</code>&#160;(resp. 
the&#160;<code>QualifierType</code>) being the URI escaped fully qualified name 
of the payload (resp. qualifier) raw type followed by the type parameters 
section delimited by angle brackets for payload parameterized type. Which leads 
to&#160;<em>unfriendly</em>&#160;URIs, e.g.:</p><div class="code panel pdl" 
style="border-width: 1px;"><div class="codeContent panelContent pdl">
 <script class="brush: text; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[cdi-event://org.apache.camel.cdi.example.EventPayload%3Cjava.lang.Integer%3E?qualifiers=org.apache.camel.cdi.example.FooQualifier%2Corg.apache.camel.cdi.example.BarQualifier]]></script>
-</div></div><p>But more fundamentally, that would prevent efficient binding 
between the endpoint instances and the observer methods as the CDI container 
doesn't have any ways of discovering the Camel context model during the 
deployment phase.</p><h3 
id="CDI-Auto-configuredOSGiintegration">Auto-configured OSGi 
integration</h3><p>The Camel context beans are automatically adapted by Camel 
CDI so that they are registered as OSGi services and the various resolvers 
(like&#160;<code>ComponentResolver</code> 
and&#160;<code>DataFormatResolver</code>) integrate with the OSGi registry. 
That means that the <a shape="rect" href="karaf.html#Karaf-Karafcommands">Karaf 
Camel commands</a> can be used to operate the Camel contexts auto-configured by 
Camel CDI, e.g.:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
+</div></div><p>But more fundamentally, that would prevent efficient binding 
between the endpoint instances and the observer methods as the CDI container 
doesn't have any ways of discovering the Camel context model during the 
deployment phase.</p><h3 
id="CDI-Auto-configuredOSGiintegration">Auto-configured OSGi 
integration</h3><p><strong>Available as of Camel 2.17</strong></p><p>The Camel 
context beans are automatically adapted by Camel CDI so that they are 
registered as OSGi services and the various resolvers 
(like&#160;<code>ComponentResolver</code> 
and&#160;<code>DataFormatResolver</code>) integrate with the OSGi registry. 
That means that the <a shape="rect" href="karaf.html#Karaf-Karafcommands">Karaf 
Camel commands</a> can be used to operate the Camel contexts auto-configured by 
Camel CDI, e.g.:</p><div class="code panel pdl" style="border-width: 1px;"><div 
class="codeContent panelContent pdl">
 <script class="brush: text; gutter: false; theme: Default" 
type="syntaxhighlighter"><![CDATA[karaf@root()&gt; camel:context-list
  Context        Status              Total #       Failed #     Inflight #   
Uptime        
  -------        ------              -------       --------     ----------   
------