Author: buildbot
Date: Sun May 5 13:18:26 2013
New Revision: 860927
Log:
Production update by buildbot for camel
Modified:
websites/production/camel/content/cache/main.pageCache
websites/production/camel/content/type-converter.html
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/type-converter.html
==============================================================================
--- websites/production/camel/content/type-converter.html (original)
+++ websites/production/camel/content/type-converter.html Sun May 5 13:18:26
2013
@@ -82,7 +82,7 @@
<ul><li>File</li><li>String</li><li>byte[] and ByteBuffer</li><li>InputStream
and OutputStream</li><li>Reader and Writer</li><li>Document and
Source</li><li>...</li></ul>
-<p>The <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html";>Message
interface</a> defines a helper method to allow conversions to be done via the
<a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html#getBody(java.lang.Class)">getBody(Class)
method</a>.</p>
+<p>The <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html";>Message
interface</a> defines a helper method to allow conversions to be done via the
<a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/Message.html#getBody(java.lang.Class)">getBody(Class)</a>
method.</p>
<p>So in an endpoint you can convert a body to another type via</p>
@@ -95,21 +95,21 @@ Document document = message.getBody(Docu
<h3><a shape="rect" name="TypeConverter-HowTypeConversionworks"></a>How Type
Conversion works</h3>
-<p>The type conversion strategy is defined by the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/TypeConverter.html";>TypeConverter</a>
interface which can be customized on a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html";>CamelContext</a>.
</p>
+<p>The type conversion strategy is defined by the <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/TypeConverter.html";>TypeConverter</a>
interface that can be customized on a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/CamelContext.html";>CamelContext</a>.
</p>
-<p>The default implementation, <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/DefaultTypeConverter.html";>DefaultTypeConverter</a>
uses pluggable strategies to load type converters via <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/TypeConverterLoader.html";>TypeConverterLoader</a>.
The default strategy, <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/AnnotationTypeConverterLoader.html";>AnnotationTypeConverterLoader</a>
uses a discovery mechanism to find converters.</p>
+<p>The default implementation, <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/DefaultTypeConverter.html";>DefaultTypeConverter</a>,
uses pluggable strategies to load type converters via <a shape="rect"
class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/TypeConverterLoader.html";>TypeConverterLoader</a>.
The default strategy, <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/AnnotationTypeConverterLoader.html";>AnnotationTypeConverterLoader</a>,
uses a discovery mechanism to find converters.</p>
<p><b>New in Camel 1.5</b></p>
-<p>The default implementation, <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/DefaultTypeConverter.html";>DefaultTypeConverter</a>
now throws a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/NoTypeConversionAvailableException.html";>NoTypeConversionAvailableException</a>
if a suitable conversion cannot be found (CAMEL-84). The semantical ambiguity
of null (both valid result and indication of no conversion found) is now
resolved, but this may impact existing code in that it should now catch the
exception instead of checking for null.</p>
+<p>The default implementation, <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/DefaultTypeConverter.html";>DefaultTypeConverter</a>,
now throws a <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/NoTypeConversionAvailableException.html";>NoTypeConversionAvailableException</a>
if a suitable conversion cannot be found (CAMEL-84). The semantical ambiguity
of <tt>null</tt> (both valid result and indication of no conversion found) is
now resolved, but this may impact existing code in that it should now catch the
exception instead of checking for <tt>null</tt>.</p>
<h3><a shape="rect"
name="TypeConverter-TypeConverterRegistry"></a>TypeConverterRegistry</h3>
<p><b>New in Camel 2.0</b></p>
-<p>Exposed the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/TypeConverterRegistry.html";>TypeConverterRegistry</a>
from <a shape="rect" href="camelcontext.html"
title="CamelContext">CamelContext</a> so end users more easily will be able to
add type converters at runtime. This is also usable in situations where the
default discovering of type converters fails, on platforms with classloading
issues. </p>
+<p>Exposed the <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/spi/TypeConverterRegistry.html";>TypeConverterRegistry</a>
from <a shape="rect" href="camelcontext.html"
title="CamelContext">CamelContext</a> so end users more easily will be able to
add type converters at runtime. This is also usable in situations where the
default discovering of type converters fails on platforms with classloading
issues. </p>
-<p>To access the registry you get it from the CamelContext</p>
+<p>To access the registry, you get it from the CamelContext</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
CamelContext context = ...
@@ -119,9 +119,9 @@ Document document = message.getBody(Docu
<h4><a shape="rect"
name="TypeConverter-TypeConverterRegistryutilizationstatistics"></a>TypeConverterRegistry
utilization statistics</h4>
-<p>Camel can gather utilization statistics of the runtime usage of type
converters. These stats is available in JMX, and ass well from the
<tt>getStatistics()</tt> method from <tt>TypeConverterRegistry</tt>.</p>
+<p>Camel can gather utilization statistics of the runtime usage of type
converters. These stats are available in JMX, and as well as from the
<tt>getStatistics()</tt> method from <tt>TypeConverterRegistry</tt>.</p>
-<p>From <b>Camel 2.11.0/2.10.5</b> onwards these statistics is default turned
off, as there is a little performance overhead under very high concurrent load.
To enable the statistics you can do this from java with:</p>
+<p>From <b>Camel 2.11.0/2.10.5</b> onwards these statistics are turned off by
default as there is some performance overhead under very high concurrent load.
To enable the statistics in Java, do the following:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
CamelContext context = ...
@@ -129,7 +129,7 @@ Document document = message.getBody(Docu
</pre>
</div></div>
-<p>Or from XML DSL by:</p>
+<p>Or in the XML DSL with:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-xml">
<span class="code-tag"><camelContext xmlns=<span
class="code-quote">"http://camel.apache.org/schema/spring";</span>
typeConverterStatisticsEnabled=<span class="code-quote">"true"</span>></span>
@@ -194,8 +194,8 @@ Document document = message.getBody(Docu
<p><b>Available in Camel 2.0</b><br clear="none">
The <a shape="rect" class="external-link"
href="http://camel.apache.org/maven/current/camel-core/apidocs/org/apache/camel/impl/converter/AnnotationTypeConverterLoader.html";>AnnotationTypeConverterLoader</a>
has been enhanced to also look for methods defined with a @FallbackConverter
annotation, and register it as a fallback type converter.</p>
-<p>Fallback type converters is used as a last resort of hopes for converting a
given value to another type. Its used when the regular type converters give
up.<br clear="none">
-The fallback converters is also meant for a broader scope so its method
signature is a bit different:</p>
+<p>Fallback type converters are used as a last resort for converting a given
value to another type. Its used when the regular type converters give up.<br
clear="none">
+The fallback converters is also meant for a broader scope, so its method
signature is a bit different:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
<pre class="code-java">
@FallbackConverter
@@ -243,7 +243,7 @@ The <tt>Exchange</tt> parameter is optio
<p>You are welcome to write your own converters. Remember to use the
@Converter annotations on the classes and methods you wish to use. Then add the
packages to a file called
<em>META-INF/services/org/apache/camel/TypeConverter</em> in your jar. Remember
to make sure that :-</p>
-<ul><li>static methods are encouraged to reduce caching; but instance methods
are fine, particularly if you want to allow optional dependency injection to
customize the converter</li><li>converter methods should be thread safe and
reentrant</li></ul>
+<ul><li>static methods are encouraged to reduce caching, but instance methods
are fine, particularly if you want to allow optional dependency injection to
customize the converter</li><li>converter methods should be thread safe and
reentrant</li></ul>
<h4><a shape="rect"
name="TypeConverter-ExamplesofTypeConverterfile"></a>Examples of TypeConverter
file</h4>
@@ -255,11 +255,11 @@ com.bar
</pre>
</div></div>
-<p>Each line in the file is package name. This tells Camel to go scan those
packages for any classes which has been annotated with the @Converter.</p>
+<p>Each line in the file is a package name. This tells Camel to go scan those
packages for any classes that has been annotated with the @Converter.</p>
<h3><a shape="rect"
name="TypeConverter-ImprovedTypeConverterbyusingFQNclassnames"></a>Improved
TypeConverter by using FQN class names</h3>
<p><b>Available as of Camel 2.8</b><br clear="none">
-In Camel 2.8 we improved the type converter loader to support specifying the
FQN class name of the converter classes. This has a much better advantage as it
avoids having to scan packages for @Converter classes. Instead it loads the
@Converter class directly. This is <b>highly</b> recommend approach to use
going forward.</p>
+In Camel 2.8 we improved the type converter loader to support specifying the
FQN class name of the converter classes. This has the advantage of avoiding
having to scan packages for @Converter classes. Instead it loads the @Converter
class directly. This is a <b>highly</b> recommend approach to use going
forward.</p>
<h4><a shape="rect"
name="TypeConverter-ExamplesofTypeConverterfile"></a>Examples of TypeConverter
file</h4>
<p>The file in the JAR:
<tt>META-INF/services/org/apache/camel/TypeConverter</tt> contains the
following line(s) for FQN class names </p>
