Author: buildbot
Date: Sun Jan 13 15:24:58 2013
New Revision: 846485

Log:
Production update by buildbot for camel

Modified:
    websites/production/camel/content/book-component-appendix.html
    websites/production/camel/content/book-in-one-page.html
    websites/production/camel/content/cache/main.pageCache
    websites/production/camel/content/camel-2110-release.html
    websites/production/camel/content/xslt.html

Modified: websites/production/camel/content/book-component-appendix.html
==============================================================================
--- websites/production/camel/content/book-component-appendix.html (original)
+++ websites/production/camel/content/book-component-appendix.html Sun Jan 13 
15:24:58 2013
@@ -17323,6 +17323,39 @@ This allows you to use xsl include and h
 
 <p>Which then will resolve the xsl file under 
<tt>org/apache/camel/component</tt>.</p>
 
+<h4><a shape="rect" 
name="BookComponentAppendix-Usingxsl%3Aincludeanddefaultprefix"></a>Using 
xsl:include and default prefix</h4>
+
+<p>When using xsl:include such as: </p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>Then in Camel 2.10.3 and older, then Camel will use "classpath:" as the 
default prefix, and load the resource from the classpath. This works for most 
cases, but if you configure the starting resource to load from file, </p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-java">
+.to(<span 
class="code-quote">"xslt:file:etc/xslt/staff_include_relative.xsl"</span>)
+</pre>
+</div></div>
+<p>.. then you would have to prefix all your includes with "file:" as well.</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"file:staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>From Camel 2.10.4 onwards we have made this easier as Camel will use the 
prefix from the endpoint configuration as the default prefix. So from Camel 
2.10.4 onwards you can do:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>Which will load the staff_template.xsl resource from the file system, as 
the endpoint was configured with "file:" as prefix.<br clear="none">
+You can still though explicit configure a prefix, and then mix and match. And 
have both file and classpath loading. But that would be unusual, as most people 
either use file or classpath based resources.</p>
+
+
 <h3><a shape="rect" 
name="BookComponentAppendix-Dynamicstylesheets"></a>Dynamic stylesheets</h3>
 <p><b>Available as of Camel 2.9</b><br clear="none">
 Camel provides the <tt>CamelXsltResourceUri</tt> header which you can use to 
define a stylesheet to use instead of what is configured on the endpoint URI. 
This allows you to provide a dynamic stylesheet at runtime.</p>

Modified: websites/production/camel/content/book-in-one-page.html
==============================================================================
--- websites/production/camel/content/book-in-one-page.html (original)
+++ websites/production/camel/content/book-in-one-page.html Sun Jan 13 15:24:58 
2013
@@ -37522,6 +37522,39 @@ This allows you to use xsl include and h
 
 <p>Which then will resolve the xsl file under 
<tt>org/apache/camel/component</tt>.</p>
 
+<h4><a shape="rect" 
name="BookInOnePage-Usingxsl%3Aincludeanddefaultprefix"></a>Using xsl:include 
and default prefix</h4>
+
+<p>When using xsl:include such as: </p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>Then in Camel 2.10.3 and older, then Camel will use "classpath:" as the 
default prefix, and load the resource from the classpath. This works for most 
cases, but if you configure the starting resource to load from file, </p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-java">
+.to(<span 
class="code-quote">"xslt:file:etc/xslt/staff_include_relative.xsl"</span>)
+</pre>
+</div></div>
+<p>.. then you would have to prefix all your includes with "file:" as well.</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"file:staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>From Camel 2.10.4 onwards we have made this easier as Camel will use the 
prefix from the endpoint configuration as the default prefix. So from Camel 
2.10.4 onwards you can do:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>Which will load the staff_template.xsl resource from the file system, as 
the endpoint was configured with "file:" as prefix.<br clear="none">
+You can still though explicit configure a prefix, and then mix and match. And 
have both file and classpath loading. But that would be unusual, as most people 
either use file or classpath based resources.</p>
+
+
 <h3><a shape="rect" name="BookInOnePage-Dynamicstylesheets"></a>Dynamic 
stylesheets</h3>
 <p><b>Available as of Camel 2.9</b><br clear="none">
 Camel provides the <tt>CamelXsltResourceUri</tt> header which you can use to 
define a stylesheet to use instead of what is configured on the endpoint URI. 
This allows you to provide a dynamic stylesheet at runtime.</p>

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

Modified: websites/production/camel/content/camel-2110-release.html
==============================================================================
--- websites/production/camel/content/camel-2110-release.html (original)
+++ websites/production/camel/content/camel-2110-release.html Sun Jan 13 
15:24:58 2013
@@ -84,7 +84,7 @@
 
 <p>Welcome to the 2.11.0 release with approximately XXX issues resolved - 
including new features, improvements, and bug fixes, such as: </p>
 
-<ul><li>Added <a shape="rect" href="binding.html" title="Binding">Binding</a> 
support, so it is easy to combine things like a <a shape="rect" 
href="data-format.html" title="Data Format">Data Format</a> to an <a 
shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> for easier 
composition of routes.</li><li>Added support for SOAP 1.2 in <a shape="rect" 
href="soap.html" title="SOAP">SOAP</a> data format.</li><li><a shape="rect" 
href="cache.html" title="Cache">Cache</a> operation for add/update now supports 
expiry headers to control time to live/idle/eternal.</li><li>Added 
<tt>allowNullBody</tt> option to <a shape="rect" href="jms.html" 
title="JMS">JMS</a> to configure whether sending messages with no body is 
allowed.</li><li>Added <tt>connectOnStartup</tt> option to <a shape="rect" 
href="hdfs.html" title="HDFS">HDFS</a> to allow to connect on demand, to avoid 
having Hadoop block for long time connecting to the HDFS cluster, as it has a 
hardcoded 15 minute retry mechan
 ism.</li><li>Added support for daily and weekly trends to <a shape="rect" 
href="twitter.html" title="Twitter">Twitter</a> component.</li><li>The <a 
shape="rect" href="camel-maven-archetypes.html" title="Camel Maven 
Archetypes">Camel Maven Archetypes</a> now generates projects without any 
license headers.</li><li>Added <tt>rejectOld</tt> option to the <a shape="rect" 
href="resequencer.html" title="Resequencer">Resequencer</a> to prevent out of 
order messages from being delivered after capacity/timeout events 
occur</li><li>Further optimized <a shape="rect" href="xpath.html" 
title="XPath">XPath</a> under concurrent load, and as well ensured resources 
are cleaned up eagerly</li><li>Added options <tt>allowNullBody</tt> and 
<tt>readLockMinLength</tt> to the <a shape="rect" href="file2.html" 
title="File2">File</a> and <a shape="rect" href="ftp2.html" 
title="FTP2">FTP</a> components.</li><li>Made <tt>changed</tt> read lock 
strategy on <a shape="rect" href="ftp2.html" title="FTP2">FT
 P</a> go faster (eg when the FTP server has a lot of files in the directory) 
if you enable the <tt>fastExistsCheck=true</tt> option as well. Notice that 
some FTP server may not support this.</li><li><a shape="rect" href="hl7.html" 
title="HL7">HL7</a> moves to HAPI 2.0 and supports using a dedicated Parser 
instance in the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec 
and DataFormat. Added "Terser" language and expression to be able to extract 
fields from a parsed message. <a shape="rect" href="hl7.html" 
title="HL7">HL7</a> now uses Apache Mina 2.x.</li><li>Add an option 
<tt>HttpMethodRestrict</tt> to restrict HTTP method in <a shape="rect" 
href="jetty.html" title="Jetty">Jetty</a> and <a shape="rect" 
href="servlet.html" title="SERVLET">SERVLET</a></li><li>Add support for 
selection of <a shape="rect" href="direct-vm.html" 
title="Direct-VM">Direct-VM</a> consumers by using ant-like path 
expression.</li><li>The <a shape="rect" href="pojo-producing.html" title="P
 OJO Producing">POJO Producing</a>, and <a shape="rect" 
href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> with 
@Consume, @Produce, @EndpointInject now supports a new {{property} attribute to 
get the endpoint configuration from a bean property (eg using a getter method); 
this allows you to configure this on the bean using conventional bean 
configuration.</li><li>Testing with <tt>camel-test-blueprint</tt> on Windows no 
longer tries to cleanup after testing taking up 5 seconds and logging 
WARNs.</li><li>The <a shape="rect" href="file2.html" title="File2">File</a>, 
and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now 
support <tt>fileExist=Move</tt> option to move any existing files before 
writing a file.</li><li>Added option <tt>loadStatisticsEnabled</tt> on <a 
shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> to allow to 
disable load statistics if not needed (avoids a background thread being in use, 
to calculate the load st
 ats).</li><li>Enabled "lazy connections" for <a shape="rect" href="xmpp.html" 
title="XMPP">XMPP</a> providers via the <tt>testConnectionOnStartup</tt> 
option</li><li>Added a connection monitor to detect and fix dropped <a 
shape="rect" href="xmpp.html" title="XMPP">XMPP</a> consumer connections at 
configurable <tt>connectionPollDelay</tt> intervals</li><li>Added an 
<tt>org.apache.camel.builder.ExchangeBuilder</tt> to build the <a shape="rect" 
href="exchange.html" title="Exchange">Exchange</a> using a builder 
pattern.</li><li>The <a shape="rect" href="camel-run-maven-goal.html" 
title="Camel Run Maven Goal">Camel Run Maven Goal</a> can now run <a 
shape="rect" href="cdi.html" title="CDI">CDI</a> applications.</li><li>The 
Camel <a shape="rect" href="cdi.html" title="CDI">CDI</a> component has 
improved a lot.</li><li>Added option <tt>allowRedeliveryWhileStopping</tt> to 
<a shape="rect" href="dead-letter-channel.html" title="Dead Letter 
Channel">error handlers</a> to control if red
 elivery is allowed during stopping/shutting down Camel or the route(s). 
Turning this option <tt>false</tt> allows to stop quicker by rejecting 
redelivery attempts.</li><li>Added support for specifying user info in Camel <a 
shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> urls, which 
contains the @ sign; now the @ sign can be given as is; without being encoded 
to %40.</li><li>Added robust connection support for <a shape="rect" 
href="jmx.html" title="JMX">JMX</a>. Optional <tt>testConnectionOnStartup</tt> 
allows a JMX consumer to attach to a JMX server that becomes available 
<em>after</em> the JMX endpoint starts; <tt>reconnectOnConnectionFailure</tt> 
enables re-connection of failed JMX connections.</li><li><a shape="rect" 
href="jaxb.html" title="JAXB">JAXB</a> and <a shape="rect" href="soap.html" 
title="SOAP">SOAP</a> data format now supports controlling namespace prefix 
mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 
etc.)</li><li>Added s
 upport for using raw uris when <a shape="rect" href="component.html" 
title="Component">Component</a>s create <a shape="rect" href="endpoint.html" 
title="Endpoint">Endpoint</a>s. This gives component writers full power in case 
their component has special syntax/notation for endpoint uri 
configurations.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s 
configured with custom <tt>AggregationStrategy</tt> will now strict check the 
custom strategy exists in the <a shape="rect" href="registry.html" 
title="Registry">Registry</a> and no longer fallback and use a default strategy 
if not.</li><li>Camel now logs on shutdown if any thread pools hasn't been 
properly shutdown, and will shutdown them as fail safe (can only be done for 
the thread pools Camel manages).</li><li>The buffer size of <a shape="rect" 
href="stream-caching.html" title="Stream caching">Stream caching</a> is now 
configurable.</li><li>Improved startup performance.</li><li>Added <a 
shape="rect" href="jms.html
 " title="JMS">JMS</a> URI option <tt>messageListenerContainerFactoryRef</tt> 
which allows you to specify a <tt>MessageListenerContainerFactory</tt> to 
determine what 
<tt>org.springframework.jms.listener.AbstractMessageListenerContainer</tt> to 
use to consume messages.</li><li><a shape="rect" href="mqtt.html" 
title="MQTT">MQTT</a> producer now leverages the <a shape="rect" 
href="asynchronous-routing-engine.html" title="Asynchronous Routing 
Engine">Asynchronous Routing Engine</a></li><li>The <a shape="rect" 
href="netty.html" title="Netty">Netty</a> producer scales up and down much 
better by leveraging a channel pool.</li><li>Added new <a shape="rect" 
href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven 
Archetypes</a> for creating Camel and Groovy applications.</li><li>Camel now 
injects <tt>CamelContext</tt> on <tt>Language</tt> and <tt>DataFormat</tt> that 
implements <tt>CamelContextAware</tt></li><li>Thread pools in Camel with 
<tt>maximumQueueSize</tt
 > of 0 or negative will now not use a worker queue but do direct hand-over to 
 > thread instead.</li><li><a shape="rect" href="simple.html" 
 > title="Simple">Simple</a> unary operators for inc and dec must now have 
 > function on left hand side, to be parsed as unary function. Otherwise its 
 > now regarded as literal.</li><li>Custom assigned id's on Camel <a 
 > shape="rect" href="routes.html" title="Routes">Routes</a> is now validated 
 > on starting the routes, that they must be unique within the same 
 > CamelContext.</li><li>Added <tt>AbstractListAggregationStrategy</tt> 
 > abstract class to make it easier to <a shape="rect" href="aggregator2.html" 
 > title="Aggregator2">aggregate</a> into a List&lt;V&gt; using a custom 
 > <tt>AggregationStrategy</tt>.</li><li><a shape="rect" href="eip.html" 
 > title="EIP">EIP</a>s which support using <tt>AggregationStrategy</tt> now 
 > control the lifecycle of the strategy; allowing end users to do custom logic 
 > in the start/stop methods of their strategy implementation.</li>
 <li>Added option <tt>includeSentJMSMessageID</tt> to <a shape="rect" 
href="jms.html" title="JMS">JMS</a> to allow to enrich Camel Message with the 
actual JMSMessageID for the sent message. Can be used by end users for logging 
purpose etc.</li><li>Added option <tt>allowShortLines</tt> and 
<tt>ignoreExtraColumns</tt> to <a shape="rect" href="flatpack-dataformat.html" 
title="Flatpack DataFormat">Flatpack data format</a>.</li><li><a shape="rect" 
href="mail.html" title="Mail">Mail</a> consumer now supports using search terms 
to filter mails by terms such as subject, from, body, sent date 
etc.</li><li>The cached script file in the <a shape="rect" href="language.html" 
title="Language">Language</a> component can now be cleared via 
JMX.</li><li>improved the karaf context-info command by adding a verbose mode 
to view endpoints list (now hidden by default) and adding stats on the number 
of active/inactive routes</li><li>Added support for <tt>UpdateList</tt>, 
<tt>DeleteList</tt> and <tt
 >ExecutorType</tt> to <a shape="rect" href="mybatis.html" 
 >title="MyBatis">MyBatis</a> component.</li><li>Added support for easier 
 >configuration of using concurrent message listener consumer when doing 
 >request/reply over <a shape="rect" href="jms.html" title="JMS">JMS</a>, by 
 >leveraging the existing <tt>concurrentConsumers</tt> and 
 ><tt>maxConcurrentConsumers</tt> options.</li><li>Improved the <a shape="rect" 
 >href="smpp.html" title="SMPP">SMPP</a> consumer to expose more data by 
 >receiving a <tt>DeliverSM</tt> message.</li><li>Camels <a shape="rect" 
 >href="using-propertyplaceholder.html" title="Using 
 >PropertyPlaceholder">property placeholders</a> can now be used in route id / 
 >node id's in the routes in XML and Java DSLs, eg &lt;route 
 >id="<tt>coolName</tt>"&gt;</li><li>The thread name pattern can easily be 
 >configured on &lt;camelContext&gt; with the new threadNamePattern 
 >attribute</li><li>Camel now validates <a shape="rect" href="seda.html" 
 >title="SEDA">SEDA</a> and <a shape="rec
 t" href="vm.html" title="VM">VM</a> endpoints using same queue name, that if 
any queue size is in use, that size must match. As well Camel logs at INFO 
level when starting up the queues and the sizes. This allows end users to 
easily spot any issues if mistakenly using different queue sizes for the same 
queue names.</li><li>Added <a shape="rect" href="camel-jmx.html" title="Camel 
JMX">JMX</a> operations to <a shape="rect" href="log.html" 
title="Log">throughput logger</a> so you can get stats and also reset the stats 
at runtime.</li><li>Added ACL support on the <a shape="rect" href="aws-s3.html" 
title="AWS-S3">AWS-S3</a> component.</li><li>Allow to configure <a shape="rect" 
href="jetty.html" title="Jetty">Jetty</a> http client thread pool settings in 
uri to make it easier to have different settings per endpoint.</li><li>Added 
support for implied decimal formats to <a shape="rect" href="bindy.html" 
title="Bindy">Bindy</a></li><li>Added option <tt>backlog</tt> to <a shape="rect"
  href="netty.html" title="Netty">Netty</a> which can be used to allow more 
concurrent clients to connect to a <a shape="rect" href="netty.html" 
title="Netty">Netty</a> consumer.</li><li>Added support for parsing CSV if a 
field has a ' (single quote) at it's beging</li><li>Added support for using 
custom url rewrite plugins in <a shape="rect" href="http.html" 
title="HTTP">HTTP</a>, <a shape="rect" href="http4.html" 
title="HTTP4">HTTP4</a>, and <a shape="rect" href="jetty.html" 
title="Jetty">Jetty</a> producers, which gives more control of url mappings, 
such as when bridging/proxying http based routes. Provided <tt><a shape="rect" 
href="urlrewrite.html" title="UrlRewrite">camel-urlrewrite</a></tt> as out of 
the box implementation.</li><li>Improved the <a shape="rect" 
href="springintegration.html" title="SpringIntegration">Spring-Integration</a> 
consumer to also send back the message headers.</li><li>The Camel <a 
shape="rect" href="guice.html" title="Guice">Guice</a> component h
 as been upgraded to latest Guice 3.0, and no longer dependent on Guice 
extension project <tt>guiceyfruit</tt>.</li><li>ReplyTo Temporary Queue now 
refreshed when the underlying <a shape="rect" href="jms.html" 
title="JMS">JMS</a> Connection fails.</li><li>When processing an <a 
shape="rect" href="exchange.html" title="Exchange">Exchange</a> fails, the 
failed route id is available for end users. See details at <a shape="rect" 
href="dead-letter-channel.html" title="Dead Letter Channel">Dead Letter 
Channel</a>.</li></ul>
+<ul><li>Added <a shape="rect" href="binding.html" title="Binding">Binding</a> 
support, so it is easy to combine things like a <a shape="rect" 
href="data-format.html" title="Data Format">Data Format</a> to an <a 
shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> for easier 
composition of routes.</li><li>Added support for SOAP 1.2 in <a shape="rect" 
href="soap.html" title="SOAP">SOAP</a> data format.</li><li><a shape="rect" 
href="cache.html" title="Cache">Cache</a> operation for add/update now supports 
expiry headers to control time to live/idle/eternal.</li><li>Added 
<tt>allowNullBody</tt> option to <a shape="rect" href="jms.html" 
title="JMS">JMS</a> to configure whether sending messages with no body is 
allowed.</li><li>Added <tt>connectOnStartup</tt> option to <a shape="rect" 
href="hdfs.html" title="HDFS">HDFS</a> to allow to connect on demand, to avoid 
having Hadoop block for long time connecting to the HDFS cluster, as it has a 
hardcoded 15 minute retry mechan
 ism.</li><li>Added support for daily and weekly trends to <a shape="rect" 
href="twitter.html" title="Twitter">Twitter</a> component.</li><li>The <a 
shape="rect" href="camel-maven-archetypes.html" title="Camel Maven 
Archetypes">Camel Maven Archetypes</a> now generates projects without any 
license headers.</li><li>Added <tt>rejectOld</tt> option to the <a shape="rect" 
href="resequencer.html" title="Resequencer">Resequencer</a> to prevent out of 
order messages from being delivered after capacity/timeout events 
occur</li><li>Further optimized <a shape="rect" href="xpath.html" 
title="XPath">XPath</a> under concurrent load, and as well ensured resources 
are cleaned up eagerly</li><li>Added options <tt>allowNullBody</tt> and 
<tt>readLockMinLength</tt> to the <a shape="rect" href="file2.html" 
title="File2">File</a> and <a shape="rect" href="ftp2.html" 
title="FTP2">FTP</a> components.</li><li>Made <tt>changed</tt> read lock 
strategy on <a shape="rect" href="ftp2.html" title="FTP2">FT
 P</a> go faster (eg when the FTP server has a lot of files in the directory) 
if you enable the <tt>fastExistsCheck=true</tt> option as well. Notice that 
some FTP server may not support this.</li><li><a shape="rect" href="hl7.html" 
title="HL7">HL7</a> moves to HAPI 2.0 and supports using a dedicated Parser 
instance in the <a shape="rect" href="hl7.html" title="HL7">HL7</a> MLLP codec 
and DataFormat. Added "Terser" language and expression to be able to extract 
fields from a parsed message. <a shape="rect" href="hl7.html" 
title="HL7">HL7</a> now uses Apache Mina 2.x.</li><li>Add an option 
<tt>HttpMethodRestrict</tt> to restrict HTTP method in <a shape="rect" 
href="jetty.html" title="Jetty">Jetty</a> and <a shape="rect" 
href="servlet.html" title="SERVLET">SERVLET</a></li><li>Add support for 
selection of <a shape="rect" href="direct-vm.html" 
title="Direct-VM">Direct-VM</a> consumers by using ant-like path 
expression.</li><li>The <a shape="rect" href="pojo-producing.html" title="P
 OJO Producing">POJO Producing</a>, and <a shape="rect" 
href="pojo-consuming.html" title="POJO Consuming">POJO Consuming</a> with 
@Consume, @Produce, @EndpointInject now supports a new {{property} attribute to 
get the endpoint configuration from a bean property (eg using a getter method); 
this allows you to configure this on the bean using conventional bean 
configuration.</li><li>Testing with <tt>camel-test-blueprint</tt> on Windows no 
longer tries to cleanup after testing taking up 5 seconds and logging 
WARNs.</li><li>The <a shape="rect" href="file2.html" title="File2">File</a>, 
and <a shape="rect" href="ftp2.html" title="FTP2">FTP</a> components now 
support <tt>fileExist=Move</tt> option to move any existing files before 
writing a file.</li><li>Added option <tt>loadStatisticsEnabled</tt> on <a 
shape="rect" href="camel-jmx.html" title="Camel JMX">Camel JMX</a> to allow to 
disable load statistics if not needed (avoids a background thread being in use, 
to calculate the load st
 ats).</li><li>Enabled "lazy connections" for <a shape="rect" href="xmpp.html" 
title="XMPP">XMPP</a> providers via the <tt>testConnectionOnStartup</tt> 
option</li><li>Added a connection monitor to detect and fix dropped <a 
shape="rect" href="xmpp.html" title="XMPP">XMPP</a> consumer connections at 
configurable <tt>connectionPollDelay</tt> intervals</li><li>Added an 
<tt>org.apache.camel.builder.ExchangeBuilder</tt> to build the <a shape="rect" 
href="exchange.html" title="Exchange">Exchange</a> using a builder 
pattern.</li><li>The <a shape="rect" href="camel-run-maven-goal.html" 
title="Camel Run Maven Goal">Camel Run Maven Goal</a> can now run <a 
shape="rect" href="cdi.html" title="CDI">CDI</a> applications.</li><li>The 
Camel <a shape="rect" href="cdi.html" title="CDI">CDI</a> component has 
improved a lot.</li><li>Added option <tt>allowRedeliveryWhileStopping</tt> to 
<a shape="rect" href="dead-letter-channel.html" title="Dead Letter 
Channel">error handlers</a> to control if red
 elivery is allowed during stopping/shutting down Camel or the route(s). 
Turning this option <tt>false</tt> allows to stop quicker by rejecting 
redelivery attempts.</li><li>Added support for specifying user info in Camel <a 
shape="rect" href="endpoint.html" title="Endpoint">Endpoint</a> urls, which 
contains the @ sign; now the @ sign can be given as is; without being encoded 
to %40.</li><li>Added robust connection support for <a shape="rect" 
href="jmx.html" title="JMX">JMX</a>. Optional <tt>testConnectionOnStartup</tt> 
allows a JMX consumer to attach to a JMX server that becomes available 
<em>after</em> the JMX endpoint starts; <tt>reconnectOnConnectionFailure</tt> 
enables re-connection of failed JMX connections.</li><li><a shape="rect" 
href="jaxb.html" title="JAXB">JAXB</a> and <a shape="rect" href="soap.html" 
title="SOAP">SOAP</a> data format now supports controlling namespace prefix 
mappings when marshalling (eg to avoid prefixes such as ns2, ns3, ns4 
etc.)</li><li>Added s
 upport for using raw uris when <a shape="rect" href="component.html" 
title="Component">Component</a>s create <a shape="rect" href="endpoint.html" 
title="Endpoint">Endpoint</a>s. This gives component writers full power in case 
their component has special syntax/notation for endpoint uri 
configurations.</li><li><a shape="rect" href="eip.html" title="EIP">EIP</a>s 
configured with custom <tt>AggregationStrategy</tt> will now strict check the 
custom strategy exists in the <a shape="rect" href="registry.html" 
title="Registry">Registry</a> and no longer fallback and use a default strategy 
if not.</li><li>Camel now logs on shutdown if any thread pools hasn't been 
properly shutdown, and will shutdown them as fail safe (can only be done for 
the thread pools Camel manages).</li><li>The buffer size of <a shape="rect" 
href="stream-caching.html" title="Stream caching">Stream caching</a> is now 
configurable.</li><li>Improved startup performance.</li><li>Added <a 
shape="rect" href="jms.html
 " title="JMS">JMS</a> URI option <tt>messageListenerContainerFactoryRef</tt> 
which allows you to specify a <tt>MessageListenerContainerFactory</tt> to 
determine what 
<tt>org.springframework.jms.listener.AbstractMessageListenerContainer</tt> to 
use to consume messages.</li><li><a shape="rect" href="mqtt.html" 
title="MQTT">MQTT</a> producer now leverages the <a shape="rect" 
href="asynchronous-routing-engine.html" title="Asynchronous Routing 
Engine">Asynchronous Routing Engine</a></li><li>The <a shape="rect" 
href="netty.html" title="Netty">Netty</a> producer scales up and down much 
better by leveraging a channel pool.</li><li>Added new <a shape="rect" 
href="camel-maven-archetypes.html" title="Camel Maven Archetypes">Camel Maven 
Archetypes</a> for creating Camel and Groovy applications.</li><li>Camel now 
injects <tt>CamelContext</tt> on <tt>Language</tt> and <tt>DataFormat</tt> that 
implements <tt>CamelContextAware</tt></li><li>Thread pools in Camel with 
<tt>maximumQueueSize</tt
 > of 0 or negative will now not use a worker queue but do direct hand-over to 
 > thread instead.</li><li><a shape="rect" href="simple.html" 
 > title="Simple">Simple</a> unary operators for inc and dec must now have 
 > function on left hand side, to be parsed as unary function. Otherwise its 
 > now regarded as literal.</li><li>Custom assigned id's on Camel <a 
 > shape="rect" href="routes.html" title="Routes">Routes</a> is now validated 
 > on starting the routes, that they must be unique within the same 
 > CamelContext.</li><li>Added <tt>AbstractListAggregationStrategy</tt> 
 > abstract class to make it easier to <a shape="rect" href="aggregator2.html" 
 > title="Aggregator2">aggregate</a> into a List&lt;V&gt; using a custom 
 > <tt>AggregationStrategy</tt>.</li><li><a shape="rect" href="eip.html" 
 > title="EIP">EIP</a>s which support using <tt>AggregationStrategy</tt> now 
 > control the lifecycle of the strategy; allowing end users to do custom logic 
 > in the start/stop methods of their strategy implementation.</li>
 <li>Added option <tt>includeSentJMSMessageID</tt> to <a shape="rect" 
href="jms.html" title="JMS">JMS</a> to allow to enrich Camel Message with the 
actual JMSMessageID for the sent message. Can be used by end users for logging 
purpose etc.</li><li>Added option <tt>allowShortLines</tt> and 
<tt>ignoreExtraColumns</tt> to <a shape="rect" href="flatpack-dataformat.html" 
title="Flatpack DataFormat">Flatpack data format</a>.</li><li><a shape="rect" 
href="mail.html" title="Mail">Mail</a> consumer now supports using search terms 
to filter mails by terms such as subject, from, body, sent date 
etc.</li><li>The cached script file in the <a shape="rect" href="language.html" 
title="Language">Language</a> component can now be cleared via 
JMX.</li><li>improved the karaf context-info command by adding a verbose mode 
to view endpoints list (now hidden by default) and adding stats on the number 
of active/inactive routes</li><li>Added support for <tt>UpdateList</tt>, 
<tt>DeleteList</tt> and <tt
 >ExecutorType</tt> to <a shape="rect" href="mybatis.html" 
 >title="MyBatis">MyBatis</a> component.</li><li>Added support for easier 
 >configuration of using concurrent message listener consumer when doing 
 >request/reply over <a shape="rect" href="jms.html" title="JMS">JMS</a>, by 
 >leveraging the existing <tt>concurrentConsumers</tt> and 
 ><tt>maxConcurrentConsumers</tt> options.</li><li>Improved the <a shape="rect" 
 >href="smpp.html" title="SMPP">SMPP</a> consumer to expose more data by 
 >receiving a <tt>DeliverSM</tt> message.</li><li>Camels <a shape="rect" 
 >href="using-propertyplaceholder.html" title="Using 
 >PropertyPlaceholder">property placeholders</a> can now be used in route id / 
 >node id's in the routes in XML and Java DSLs, eg &lt;route 
 >id="<tt>coolName</tt>"&gt;</li><li>The thread name pattern can easily be 
 >configured on &lt;camelContext&gt; with the new threadNamePattern 
 >attribute</li><li>Camel now validates <a shape="rect" href="seda.html" 
 >title="SEDA">SEDA</a> and <a shape="rec
 t" href="vm.html" title="VM">VM</a> endpoints using same queue name, that if 
any queue size is in use, that size must match. As well Camel logs at INFO 
level when starting up the queues and the sizes. This allows end users to 
easily spot any issues if mistakenly using different queue sizes for the same 
queue names.</li><li>Added <a shape="rect" href="camel-jmx.html" title="Camel 
JMX">JMX</a> operations to <a shape="rect" href="log.html" 
title="Log">throughput logger</a> so you can get stats and also reset the stats 
at runtime.</li><li>Added ACL support on the <a shape="rect" href="aws-s3.html" 
title="AWS-S3">AWS-S3</a> component.</li><li>Allow to configure <a shape="rect" 
href="jetty.html" title="Jetty">Jetty</a> http client thread pool settings in 
uri to make it easier to have different settings per endpoint.</li><li>Added 
support for implied decimal formats to <a shape="rect" href="bindy.html" 
title="Bindy">Bindy</a></li><li>Added option <tt>backlog</tt> to <a shape="rect"
  href="netty.html" title="Netty">Netty</a> which can be used to allow more 
concurrent clients to connect to a <a shape="rect" href="netty.html" 
title="Netty">Netty</a> consumer.</li><li>Added support for parsing CSV if a 
field has a ' (single quote) at it's beging</li><li>Added support for using 
custom url rewrite plugins in <a shape="rect" href="http.html" 
title="HTTP">HTTP</a>, <a shape="rect" href="http4.html" 
title="HTTP4">HTTP4</a>, and <a shape="rect" href="jetty.html" 
title="Jetty">Jetty</a> producers, which gives more control of url mappings, 
such as when bridging/proxying http based routes. Provided <tt><a shape="rect" 
href="urlrewrite.html" title="UrlRewrite">camel-urlrewrite</a></tt> as out of 
the box implementation.</li><li>Improved the <a shape="rect" 
href="springintegration.html" title="SpringIntegration">Spring-Integration</a> 
consumer to also send back the message headers.</li><li>The Camel <a 
shape="rect" href="guice.html" title="Guice">Guice</a> component h
 as been upgraded to latest Guice 3.0, and no longer dependent on Guice 
extension project <tt>guiceyfruit</tt>.</li><li>ReplyTo Temporary Queue now 
refreshed when the underlying <a shape="rect" href="jms.html" 
title="JMS">JMS</a> Connection fails.</li><li>When processing an <a 
shape="rect" href="exchange.html" title="Exchange">Exchange</a> fails, the 
failed route id is available for end users. See details at <a shape="rect" 
href="dead-letter-channel.html" title="Dead Letter Channel">Dead Letter 
Channel</a>.</li><li>When using <a shape="rect" href="xslt.html" 
title="XSLT">XSLT</a> includes will use same file or classpath loading as 
endpoint configuration, if not explicit configured.</li></ul>
 
 
 
@@ -151,7 +151,7 @@
 
 <h2><a shape="rect" 
name="Camel2.11.0Release-Importantchangestoconsiderwhenupgrading"></a>Important 
changes to consider when upgrading</h2>
 
-<ul><li>Spring 3.0.x support is @deprecated and some of the camel-spring 
components require Spring 3.1 onwards.</li><li>Apache Camel Karaf features now 
uses Spring version range "[3.1,4)" as Spring 3.1 is now required as minimum 
Spring version.</li><li><tt>camel-mina2</tt> now uses 
<tt>OrderedThreadPoolExecutor</tt> by default. There is a new option 
<tt>orderedThreadPoolExecutor</tt> you can configure it to <tt>false</tt> to 
revert back to unordered if needed. If using SSL etc. then ordered is required 
to be used.</li><li><tt>camel-netty</tt> now uses 
<tt>OrderedMemoryAwareThreadPoolExecutor</tt> by default. There is a new option 
<tt>orderedThreadPoolExecutor</tt> you can configure it to false to revert back 
to unordered if needed. If using SSL etc. then ordered is required to be 
used.</li><li>The default value of the <tt>delay</tt> option on <a shape="rect" 
href="timer.html" title="Timer">Timer</a> has been changed from <tt>0</tt> to 
<tt>1000</tt></li><li>The default value 
 of the <tt>convertLFtoCR</tt> option of the <a shape="rect" href="hl7.html" 
title="HL7">HL7</a> MLLP codec has been changed from <tt>true</tt> to 
<tt>false</tt>. Likewise, the <a shape="rect" href="hl7.html" 
title="HL7">HL7</a> DataFormat and TypeConverter do not perform this conversion 
anymore.</li><li>The <a shape="rect" href="simple.html" 
title="Simple">Simple</a> language has limited its support for the escape 
character to only new line, carriage return and tab characters. This makes it 
easier to use back-slash characters in the <a shape="rect" href="simple.html" 
title="Simple">Simple</a> language without double escaping 
etc.</li><li><tt>camel-netty</tt> now requires <tt>commons-pool</tt> as 
dependency.</li><li>The <tt>maximumQueueSize</tt> of <a shape="rect" 
class="external-link" 
href="http://camel.apache.org/threading-model.html";>Thread Pools</a> and <a 
shape="rect" class="external-link" 
href="http://camel.apache.org/threading-model.html";>Thread Pool Profiles</a> 
with 
 values 0 or negative now means disable the worker queue, and use 
direct-handover. If you want an unbounded queue size, then set the 
<tt>maximumQueueSize</tt> to <tt>Integer.MAX_VALUE</tt> which was what the 
previous code did.</li><li>Custom assigned id's on Camel <a shape="rect" 
href="routes.html" title="Routes">Routes</a> is now validated on starting the 
routes, that they must be unique within the same 
CamelContext.</li><li><tt>camel-blueprint</tt> now requires Apache Aries 1.0, 
and OSGi 4.3.0.</li><li>Removed @deprecated classes form <tt>camel-spring</tt> 
in the <tt>org.apache.camel.component</tt> package which was causing 
split-package issue with OSGi. Component authors who are using these 
@deprecated classes, should migrate to use equivalent classes from 
<tt>camel-core</tt> in the same package.</li><li>The default Spring version is 
upgraded from 3.0.7 to 3.1.3 out of the box.</li><li>Camel now validates <a 
shape="rect" href="seda.html" title="SEDA">SEDA</a> and <a shape=
 "rect" href="vm.html" title="VM">VM</a> endpoints using same queue name, that 
if any queue size is in use, that size must match. As well Camel logs at INFO 
level when starting up the queues and the sizes. This allows end users to 
easily spot any issues if mistakenly using different queue sizes for the same 
queue names.</li><li>The <a shape="rect" href="zookeeper.html" 
title="Zookeeper">Zookeeper endpoint</a> <tt>awaitExistence</tt> option has 
been marked as @deprecated and is removed from it's documentation as it's usage 
would have no effect in the current codebase.</li><li>Marked the 2 classes in 
the <tt>junit4</tt> package from <tt>camel-test-spring</tt> component as 
@deprecated, and refer to use the classes from the <tt>spring</tt> package 
instead.</li></ul>
+<ul><li>Spring 3.0.x support is @deprecated and some of the camel-spring 
components require Spring 3.1 onwards.</li><li>Apache Camel Karaf features now 
uses Spring version range "[3.1,4)" as Spring 3.1 is now required as minimum 
Spring version.</li><li><tt>camel-mina2</tt> now uses 
<tt>OrderedThreadPoolExecutor</tt> by default. There is a new option 
<tt>orderedThreadPoolExecutor</tt> you can configure it to <tt>false</tt> to 
revert back to unordered if needed. If using SSL etc. then ordered is required 
to be used.</li><li><tt>camel-netty</tt> now uses 
<tt>OrderedMemoryAwareThreadPoolExecutor</tt> by default. There is a new option 
<tt>orderedThreadPoolExecutor</tt> you can configure it to false to revert back 
to unordered if needed. If using SSL etc. then ordered is required to be 
used.</li><li>The default value of the <tt>delay</tt> option on <a shape="rect" 
href="timer.html" title="Timer">Timer</a> has been changed from <tt>0</tt> to 
<tt>1000</tt></li><li>The default value 
 of the <tt>convertLFtoCR</tt> option of the <a shape="rect" href="hl7.html" 
title="HL7">HL7</a> MLLP codec has been changed from <tt>true</tt> to 
<tt>false</tt>. Likewise, the <a shape="rect" href="hl7.html" 
title="HL7">HL7</a> DataFormat and TypeConverter do not perform this conversion 
anymore.</li><li>The <a shape="rect" href="simple.html" 
title="Simple">Simple</a> language has limited its support for the escape 
character to only new line, carriage return and tab characters. This makes it 
easier to use back-slash characters in the <a shape="rect" href="simple.html" 
title="Simple">Simple</a> language without double escaping 
etc.</li><li><tt>camel-netty</tt> now requires <tt>commons-pool</tt> as 
dependency.</li><li>The <tt>maximumQueueSize</tt> of <a shape="rect" 
class="external-link" 
href="http://camel.apache.org/threading-model.html";>Thread Pools</a> and <a 
shape="rect" class="external-link" 
href="http://camel.apache.org/threading-model.html";>Thread Pool Profiles</a> 
with 
 values 0 or negative now means disable the worker queue, and use 
direct-handover. If you want an unbounded queue size, then set the 
<tt>maximumQueueSize</tt> to <tt>Integer.MAX_VALUE</tt> which was what the 
previous code did.</li><li>Custom assigned id's on Camel <a shape="rect" 
href="routes.html" title="Routes">Routes</a> is now validated on starting the 
routes, that they must be unique within the same 
CamelContext.</li><li><tt>camel-blueprint</tt> now requires Apache Aries 1.0, 
and OSGi 4.3.0.</li><li>Removed @deprecated classes form <tt>camel-spring</tt> 
in the <tt>org.apache.camel.component</tt> package which was causing 
split-package issue with OSGi. Component authors who are using these 
@deprecated classes, should migrate to use equivalent classes from 
<tt>camel-core</tt> in the same package.</li><li>The default Spring version is 
upgraded from 3.0.7 to 3.1.3 out of the box.</li><li>Camel now validates <a 
shape="rect" href="seda.html" title="SEDA">SEDA</a> and <a shape=
 "rect" href="vm.html" title="VM">VM</a> endpoints using same queue name, that 
if any queue size is in use, that size must match. As well Camel logs at INFO 
level when starting up the queues and the sizes. This allows end users to 
easily spot any issues if mistakenly using different queue sizes for the same 
queue names.</li><li>The <a shape="rect" href="zookeeper.html" 
title="Zookeeper">Zookeeper endpoint</a> <tt>awaitExistence</tt> option has 
been marked as @deprecated and is removed from it's documentation as it's usage 
would have no effect in the current codebase.</li><li>Marked the 2 classes in 
the <tt>junit4</tt> package from <tt>camel-test-spring</tt> component as 
@deprecated, and refer to use the classes from the <tt>spring</tt> package 
instead.</li><li>If using <a shape="rect" href="xslt.html" 
title="XSLT">XSLT</a> with includes, then mind that if not explicit defined 
file: or classpath: as prefix in xsl:include, then Camel will now use the same 
as configured on the e
 ndpoint. Before "classpath:" was always used as fallback, despite endpoint 
could have been configured with "file:".</li></ul>
 
 
 <h2><a shape="rect" name="Camel2.11.0Release-Notice"></a>Notice</h2>

Modified: websites/production/camel/content/xslt.html
==============================================================================
--- websites/production/camel/content/xslt.html (original)
+++ websites/production/camel/content/xslt.html Sun Jan 13 15:24:58 2013
@@ -232,6 +232,39 @@ This allows you to use xsl include and h
 
 <p>Which then will resolve the xsl file under 
<tt>org/apache/camel/component</tt>.</p>
 
+<h4><a shape="rect" name="XSLT-Usingxsl%3Aincludeanddefaultprefix"></a>Using 
xsl:include and default prefix</h4>
+
+<p>When using xsl:include such as: </p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>Then in Camel 2.10.3 and older, then Camel will use "classpath:" as the 
default prefix, and load the resource from the classpath. This works for most 
cases, but if you configure the starting resource to load from file, </p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-java">
+.to(<span 
class="code-quote">"xslt:file:etc/xslt/staff_include_relative.xsl"</span>)
+</pre>
+</div></div>
+<p>.. then you would have to prefix all your includes with "file:" as well.</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"file:staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>From Camel 2.10.4 onwards we have made this easier as Camel will use the 
prefix from the endpoint configuration as the default prefix. So from Camel 
2.10.4 onwards you can do:</p>
+<div class="code panel" style="border-width: 1px;"><div class="codeContent 
panelContent">
+<pre class="code-xml">
+<span class="code-tag">&lt;<span class="code-keyword">xsl:include</span> 
href=<span class="code-quote">"staff_template.xsl"</span>/&gt;</span>
+</pre>
+</div></div>
+
+<p>Which will load the staff_template.xsl resource from the file system, as 
the endpoint was configured with "file:" as prefix.<br clear="none">
+You can still though explicit configure a prefix, and then mix and match. And 
have both file and classpath loading. But that would be unusual, as most people 
either use file or classpath based resources.</p>
+
+
 <h3><a shape="rect" name="XSLT-Dynamicstylesheets"></a>Dynamic stylesheets</h3>
 <p><b>Available as of Camel 2.9</b><br clear="none">
 Camel provides the <tt>CamelXsltResourceUri</tt> header which you can use to 
define a stylesheet to use instead of what is configured on the endpoint URI. 
This allows you to provide a dynamic stylesheet at runtime.</p>


Reply via email to