Author: buildbot
Date: Tue Apr 24 14:20:58 2012
New Revision: 814237
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/servlet.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 Tue Apr 24
14:20:58 2012
@@ -14153,8 +14153,10 @@ servlet:<span class="code-comment">//rel
<p>You can consume only from endpoints generated by the Servlet component.
Therefore, it should be used only as input into your Camel routes. To issue
HTTP requests against other HTTP endpoints, use the <a shape="rect"
href="http.html" title="HTTP">HTTP Component</a></p>
-<h3><a shape="rect"
name="BookComponentAppendix-UsingmultipleCamelapplicationsinthesameservletcontainer"></a>Using
multiple Camel applications in the same servlet container</h3>
-<p>If you use multiple Camel applications in the same servlet container, then
there will be an issue when using the default servlet name, as it would not be
able to properly differentiate between multiple Camel applications.</p>
+<h3><a shape="rect"
name="BookComponentAppendix-PuttingCamelJARsintheappserverbootclasspath"></a>Putting
Camel JARs in the app server boot classpath</h3>
+<p>If you put the Camel JARs such as <tt>camel-core</tt>,
<tt>camel-servlet</tt>, etc. in the boot classpath of your application server
(eg usually in its lib directory), then mind that the servlet mapping list is
now shared between multiple deployed Camel application in the app server.</p>
+
+<p>Mind that putting Camel JARs in the boot classpath of the application
server is generally not best practice!</p>
<p>So in those situations you <b>must</b> define a custom and unique servlet
name in each of your Camel application, eg in the <tt>web.xml</tt> define:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
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 Tue Apr 24 14:20:58
2012
@@ -34363,8 +34363,10 @@ servlet:<span class="code-comment">//rel
<p>You can consume only from endpoints generated by the Servlet component.
Therefore, it should be used only as input into your Camel routes. To issue
HTTP requests against other HTTP endpoints, use the <a shape="rect"
href="http.html" title="HTTP">HTTP Component</a></p>
-<h3><a shape="rect"
name="BookInOnePage-UsingmultipleCamelapplicationsinthesameservletcontainer"></a>Using
multiple Camel applications in the same servlet container</h3>
-<p>If you use multiple Camel applications in the same servlet container, then
there will be an issue when using the default servlet name, as it would not be
able to properly differentiate between multiple Camel applications.</p>
+<h3><a shape="rect"
name="BookInOnePage-PuttingCamelJARsintheappserverbootclasspath"></a>Putting
Camel JARs in the app server boot classpath</h3>
+<p>If you put the Camel JARs such as <tt>camel-core</tt>,
<tt>camel-servlet</tt>, etc. in the boot classpath of your application server
(eg usually in its lib directory), then mind that the servlet mapping list is
now shared between multiple deployed Camel application in the app server.</p>
+
+<p>Mind that putting Camel JARs in the boot classpath of the application
server is generally not best practice!</p>
<p>So in those situations you <b>must</b> define a custom and unique servlet
name in each of your Camel application, eg in the <tt>web.xml</tt> define:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
Modified: websites/production/camel/content/cache/main.pageCache
==============================================================================
Binary files - no diff available.
Modified: websites/production/camel/content/servlet.html
==============================================================================
--- websites/production/camel/content/servlet.html (original)
+++ websites/production/camel/content/servlet.html Tue Apr 24 14:20:58 2012
@@ -119,8 +119,10 @@ servlet:<span class="code-comment">//rel
<p>You can consume only from endpoints generated by the Servlet component.
Therefore, it should be used only as input into your Camel routes. To issue
HTTP requests against other HTTP endpoints, use the <a shape="rect"
href="http.html" title="HTTP">HTTP Component</a></p>
-<h3><a shape="rect"
name="SERVLET-UsingmultipleCamelapplicationsinthesameservletcontainer"></a>Using
multiple Camel applications in the same servlet container</h3>
-<p>If you use multiple Camel applications in the same servlet container, then
there will be an issue when using the default servlet name, as it would not be
able to properly differentiate between multiple Camel applications.</p>
+<h3><a shape="rect"
name="SERVLET-PuttingCamelJARsintheappserverbootclasspath"></a>Putting Camel
JARs in the app server boot classpath</h3>
+<p>If you put the Camel JARs such as <tt>camel-core</tt>,
<tt>camel-servlet</tt>, etc. in the boot classpath of your application server
(eg usually in its lib directory), then mind that the servlet mapping list is
now shared between multiple deployed Camel application in the app server.</p>
+
+<p>Mind that putting Camel JARs in the boot classpath of the application
server is generally not best practice!</p>
<p>So in those situations you <b>must</b> define a custom and unique servlet
name in each of your Camel application, eg in the <tt>web.xml</tt> define:</p>
<div class="code panel" style="border-width: 1px;"><div class="codeContent
panelContent">
