You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@servicemix.apache.org by ge...@apache.org on 2013/02/08 21:35:05 UTC

svn commit: r1444219 [1/20] - in /servicemix/site/production/docs/4.4.x: ./ activemq/ architecture/ camel/ camel/deployment/ commands/ developers-guide/ images/ jbi/ jbi/components/ karaf/developers-guide/ karaf/users-guide/ nmr/ quickstart/ user/ user...

Author: gertv
Date: Fri Feb  8 20:35:02 2013
New Revision: 1444219

URL: http://svn.apache.org/r1444219
Log:
[scm-publish] Updating ServiceMix 4.4.x documentation contents

Added:
    servicemix/site/production/docs/4.4.x/developers-guide/
    servicemix/site/production/docs/4.4.x/developers-guide/connect-console.html
    servicemix/site/production/docs/4.4.x/developers-guide/creating-bundles.html
    servicemix/site/production/docs/4.4.x/developers-guide/custom-distribution.html
    servicemix/site/production/docs/4.4.x/developers-guide/debugging.html
    servicemix/site/production/docs/4.4.x/developers-guide/developer-commands.html
    servicemix/site/production/docs/4.4.x/developers-guide/extending-console.html
    servicemix/site/production/docs/4.4.x/developers-guide/features-maven-plugin-add.html
    servicemix/site/production/docs/4.4.x/developers-guide/features-maven-plugin-generate.html
    servicemix/site/production/docs/4.4.x/developers-guide/features-maven-plugin-validate.html
    servicemix/site/production/docs/4.4.x/developers-guide/features-maven-plugin.html
    servicemix/site/production/docs/4.4.x/developers-guide/index.html
    servicemix/site/production/docs/4.4.x/developers-guide/shell-syntax.html
    servicemix/site/production/docs/4.4.x/developers-guide/toc.html
    servicemix/site/production/docs/4.4.x/developers-guide/writing-tests.html
    servicemix/site/production/docs/4.4.x/images/smx-overview.dia   (with props)
    servicemix/site/production/docs/4.4.x/images/smx-overview.png   (with props)
    servicemix/site/production/docs/4.4.x/user/
    servicemix/site/production/docs/4.4.x/user/index.html
    servicemix/site/production/docs/4.4.x/user/technology-selection.html
    servicemix/site/production/docs/4.4.x/user/toc.html
    servicemix/site/production/docs/4.4.x/user/what-is-smx4.html
    servicemix/site/production/docs/4.4.x/users-guide/
    servicemix/site/production/docs/4.4.x/users-guide/child-instances.html
    servicemix/site/production/docs/4.4.x/users-guide/colorized-console.html
    servicemix/site/production/docs/4.4.x/users-guide/configuration.html
    servicemix/site/production/docs/4.4.x/users-guide/deployer.html
    servicemix/site/production/docs/4.4.x/users-guide/directory-structure.html
    servicemix/site/production/docs/4.4.x/users-guide/failover.html
    servicemix/site/production/docs/4.4.x/users-guide/http.html
    servicemix/site/production/docs/4.4.x/users-guide/index.html
    servicemix/site/production/docs/4.4.x/users-guide/installation.html
    servicemix/site/production/docs/4.4.x/users-guide/jmx.html
    servicemix/site/production/docs/4.4.x/users-guide/jre-tuning.html
    servicemix/site/production/docs/4.4.x/users-guide/kar.html
    servicemix/site/production/docs/4.4.x/users-guide/logging-system.html
    servicemix/site/production/docs/4.4.x/users-guide/provisioning.html
    servicemix/site/production/docs/4.4.x/users-guide/remote-console.html
    servicemix/site/production/docs/4.4.x/users-guide/security.html
    servicemix/site/production/docs/4.4.x/users-guide/start-stop.html
    servicemix/site/production/docs/4.4.x/users-guide/toc.html
    servicemix/site/production/docs/4.4.x/users-guide/using-console.html
    servicemix/site/production/docs/4.4.x/users-guide/web-applications.html
    servicemix/site/production/docs/4.4.x/users-guide/web-console.html
    servicemix/site/production/docs/4.4.x/users-guide/wrapper.html
Removed:
    servicemix/site/production/docs/4.4.x/architecture/
    servicemix/site/production/docs/4.4.x/karaf/developers-guide/
    servicemix/site/production/docs/4.4.x/karaf/users-guide/
Modified:
    servicemix/site/production/docs/4.4.x/activemq/index.html
    servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf
    servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf.html
    servicemix/site/production/docs/4.4.x/camel/deployment/index.html
    servicemix/site/production/docs/4.4.x/camel/index.html
    servicemix/site/production/docs/4.4.x/camel/troubleshooting.html
    servicemix/site/production/docs/4.4.x/commands/admin-change-opts.html
    servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-registry-port.html
    servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-server-port.html
    servicemix/site/production/docs/4.4.x/commands/admin-change-ssh-port.html
    servicemix/site/production/docs/4.4.x/commands/admin-connect.html
    servicemix/site/production/docs/4.4.x/commands/admin-create.html
    servicemix/site/production/docs/4.4.x/commands/admin-destroy.html
    servicemix/site/production/docs/4.4.x/commands/admin-list.html
    servicemix/site/production/docs/4.4.x/commands/admin-rename.html
    servicemix/site/production/docs/4.4.x/commands/admin-start.html
    servicemix/site/production/docs/4.4.x/commands/admin-stop.html
    servicemix/site/production/docs/4.4.x/commands/commands.html
    servicemix/site/production/docs/4.4.x/commands/config-cancel.html
    servicemix/site/production/docs/4.4.x/commands/config-delete.html
    servicemix/site/production/docs/4.4.x/commands/config-edit.html
    servicemix/site/production/docs/4.4.x/commands/config-list.html
    servicemix/site/production/docs/4.4.x/commands/config-propappend.html
    servicemix/site/production/docs/4.4.x/commands/config-propdel.html
    servicemix/site/production/docs/4.4.x/commands/config-proplist.html
    servicemix/site/production/docs/4.4.x/commands/config-propset.html
    servicemix/site/production/docs/4.4.x/commands/config-update.html
    servicemix/site/production/docs/4.4.x/commands/dev-create-dump.html
    servicemix/site/production/docs/4.4.x/commands/dev-dynamic-import.html
    servicemix/site/production/docs/4.4.x/commands/dev-framework.html
    servicemix/site/production/docs/4.4.x/commands/dev-print-stack-traces.html
    servicemix/site/production/docs/4.4.x/commands/dev-restart.html
    servicemix/site/production/docs/4.4.x/commands/dev-show-tree.html
    servicemix/site/production/docs/4.4.x/commands/dev-watch.html
    servicemix/site/production/docs/4.4.x/commands/features-addUrl.html
    servicemix/site/production/docs/4.4.x/commands/features-info.html
    servicemix/site/production/docs/4.4.x/commands/features-install.html
    servicemix/site/production/docs/4.4.x/commands/features-list.html
    servicemix/site/production/docs/4.4.x/commands/features-listRepositories.html
    servicemix/site/production/docs/4.4.x/commands/features-listUrl.html
    servicemix/site/production/docs/4.4.x/commands/features-listVersions.html
    servicemix/site/production/docs/4.4.x/commands/features-refreshUrl.html
    servicemix/site/production/docs/4.4.x/commands/features-removeRepository.html
    servicemix/site/production/docs/4.4.x/commands/features-removeUrl.html
    servicemix/site/production/docs/4.4.x/commands/features-uninstall.html
    servicemix/site/production/docs/4.4.x/commands/jaas-cancel.html
    servicemix/site/production/docs/4.4.x/commands/jaas-manage.html
    servicemix/site/production/docs/4.4.x/commands/jaas-pending.html
    servicemix/site/production/docs/4.4.x/commands/jaas-realms.html
    servicemix/site/production/docs/4.4.x/commands/jaas-roleadd.html
    servicemix/site/production/docs/4.4.x/commands/jaas-roledel.html
    servicemix/site/production/docs/4.4.x/commands/jaas-update.html
    servicemix/site/production/docs/4.4.x/commands/jaas-useradd.html
    servicemix/site/production/docs/4.4.x/commands/jaas-userdel.html
    servicemix/site/production/docs/4.4.x/commands/jaas-users.html
    servicemix/site/production/docs/4.4.x/commands/log-clear.html
    servicemix/site/production/docs/4.4.x/commands/log-display-exception.html
    servicemix/site/production/docs/4.4.x/commands/log-display.html
    servicemix/site/production/docs/4.4.x/commands/log-get.html
    servicemix/site/production/docs/4.4.x/commands/log-set.html
    servicemix/site/production/docs/4.4.x/commands/log-tail.html
    servicemix/site/production/docs/4.4.x/commands/obr-addUrl.html
    servicemix/site/production/docs/4.4.x/commands/obr-deploy.html
    servicemix/site/production/docs/4.4.x/commands/obr-find.html
    servicemix/site/production/docs/4.4.x/commands/obr-info.html
    servicemix/site/production/docs/4.4.x/commands/obr-list.html
    servicemix/site/production/docs/4.4.x/commands/obr-listUrl.html
    servicemix/site/production/docs/4.4.x/commands/obr-refreshUrl.html
    servicemix/site/production/docs/4.4.x/commands/obr-removeUrl.html
    servicemix/site/production/docs/4.4.x/commands/obr-resolve.html
    servicemix/site/production/docs/4.4.x/commands/obr-source.html
    servicemix/site/production/docs/4.4.x/commands/obr-start.html
    servicemix/site/production/docs/4.4.x/commands/osgi-bundle-level.html
    servicemix/site/production/docs/4.4.x/commands/osgi-headers.html
    servicemix/site/production/docs/4.4.x/commands/osgi-info.html
    servicemix/site/production/docs/4.4.x/commands/osgi-install.html
    servicemix/site/production/docs/4.4.x/commands/osgi-list.html
    servicemix/site/production/docs/4.4.x/commands/osgi-ls.html
    servicemix/site/production/docs/4.4.x/commands/osgi-refresh.html
    servicemix/site/production/docs/4.4.x/commands/osgi-resolve.html
    servicemix/site/production/docs/4.4.x/commands/osgi-restart.html
    servicemix/site/production/docs/4.4.x/commands/osgi-shutdown.html
    servicemix/site/production/docs/4.4.x/commands/osgi-start-level.html
    servicemix/site/production/docs/4.4.x/commands/osgi-start.html
    servicemix/site/production/docs/4.4.x/commands/osgi-stop.html
    servicemix/site/production/docs/4.4.x/commands/osgi-uninstall.html
    servicemix/site/production/docs/4.4.x/commands/osgi-update.html
    servicemix/site/production/docs/4.4.x/commands/packages-exports.html
    servicemix/site/production/docs/4.4.x/commands/packages-imports.html
    servicemix/site/production/docs/4.4.x/commands/shell-cat.html
    servicemix/site/production/docs/4.4.x/commands/shell-clear.html
    servicemix/site/production/docs/4.4.x/commands/shell-each.html
    servicemix/site/production/docs/4.4.x/commands/shell-echo.html
    servicemix/site/production/docs/4.4.x/commands/shell-exec.html
    servicemix/site/production/docs/4.4.x/commands/shell-grep.html
    servicemix/site/production/docs/4.4.x/commands/shell-head.html
    servicemix/site/production/docs/4.4.x/commands/shell-history.html
    servicemix/site/production/docs/4.4.x/commands/shell-if.html
    servicemix/site/production/docs/4.4.x/commands/shell-info.html
    servicemix/site/production/docs/4.4.x/commands/shell-java.html
    servicemix/site/production/docs/4.4.x/commands/shell-logout.html
    servicemix/site/production/docs/4.4.x/commands/shell-more.html
    servicemix/site/production/docs/4.4.x/commands/shell-new.html
    servicemix/site/production/docs/4.4.x/commands/shell-printf.html
    servicemix/site/production/docs/4.4.x/commands/shell-sleep.html
    servicemix/site/production/docs/4.4.x/commands/shell-sort.html
    servicemix/site/production/docs/4.4.x/commands/shell-source.html
    servicemix/site/production/docs/4.4.x/commands/shell-tac.html
    servicemix/site/production/docs/4.4.x/commands/shell-tail.html
    servicemix/site/production/docs/4.4.x/commands/ssh-ssh.html
    servicemix/site/production/docs/4.4.x/commands/ssh-sshd.html
    servicemix/site/production/docs/4.4.x/commands/web-list.html
    servicemix/site/production/docs/4.4.x/commands/wrapper-install.html
    servicemix/site/production/docs/4.4.x/index.html
    servicemix/site/production/docs/4.4.x/jbi/components/index.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-bean.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-camel.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-cxf-bc.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-cxf-se.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-drools.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-eip.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-file.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-ftp.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-http.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-jms.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-mail.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-osworkflow.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-quartz.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-saxon.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-scripting.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-snmp.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-validation.html
    servicemix/site/production/docs/4.4.x/jbi/components/servicemix-vfs.html
    servicemix/site/production/docs/4.4.x/jbi/index.html
    servicemix/site/production/docs/4.4.x/jbi/jbi-guide.pdf
    servicemix/site/production/docs/4.4.x/jbi/jbi-guide.pdf.html
    servicemix/site/production/docs/4.4.x/nmr/index.html
    servicemix/site/production/docs/4.4.x/nmr/nmr-camel.html
    servicemix/site/production/docs/4.4.x/nmr/nmr-event-listeners.html
    servicemix/site/production/docs/4.4.x/nmr/toc.html
    servicemix/site/production/docs/4.4.x/quickstart/console.html
    servicemix/site/production/docs/4.4.x/quickstart/features.html
    servicemix/site/production/docs/4.4.x/quickstart/installation.html
    servicemix/site/production/docs/4.4.x/quickstart/quickstart.pdf
    servicemix/site/production/docs/4.4.x/quickstart/quickstart.pdf.html

Modified: servicemix/site/production/docs/4.4.x/activemq/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/activemq/index.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/activemq/index.html (original)
+++ servicemix/site/production/docs/4.4.x/activemq/index.html Fri Feb  8 20:35:02 2013
@@ -77,7 +77,7 @@
 </ul>
         </div>
         <div id="body">
-                    <h2 id="IntroducingActiveMQ">Introducing ActiveMQ</h2><p>Apache ActiveMQ is the most popular and powerful open source messaging and Integration Patterns provider.<br/>Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols<br/>and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License</p><h3 id="ActiveMQSupports">ActiveMQ Supports</h3><h4 id="EasycommunicationviaCrossLanguageClients">Easy communication via Cross Language Clients</h4><ul><li>ActiveMQ C++ Clients</li><li>Ajax</li><li>C Integration</li><li>CMS</li><li>Delphi and FreePascal</li><li>dot Net</li><li>Perl</li><li>PHP</li><li>Pike</li><li>Python</li><li>Ruby</li><li>WebSockets</li><li>JMS to JMS Bridge</li></ul><h4 id="SeveralProtocols">Several Protocols</h4><ul><li>AMQP</li><li>OpenWire</li><li>REST</li><li>RSS and Atom</li><li>Stomp</li><li>WSIF</li><li>WS Notification</li><li>XMPP</li></ul><h3 id="UsingAc
 tiveMQfromServiceMix">Using ActiveMQ from ServiceMix</h3><p>To start using ActiveMQ from your code, simply get a hold of the connection pool declared in the activemq-broker.xml file.<br/>If you want to use ActiveMQ as a JBI component, configure servicemix-jms. You can also utilize ActiveMQ from Camel via the<br/>camel-jms component.</p><h3 id="WhenshouldIuseActiveMQ">When should I use ActiveMQ?</h3><p>Whenever you have a unit of work or payload that you could process asynchronously, you would like to have multiple recipients,<br/>concurrent competing recipients to scale or leverage multiple processing units. If you want to spread load across multiple<br/>system boundaries. You want to cluster or provide fail over and messaging security, you have long running flows.</p><p>In any of these instances it would be strongly suggested you evaluate what a scalable and secure messaging solution can bring to the table.</p><h3 id="Commonusecases">Common use cases</h3><p>Integration with
  other systems, since you can pass messages in and out of ActiveMQ from pretty much any programming language<br/>it is very simple to start integrating heterogeneous environments.</p><p>Providing an event driven architecture. You can develop your solutions based on actions as opposed to looking for data or<br/>relying on completely synchronous behaviour.</p><p>Providing infrastructure for messaging across large distances, leverage the network connectors and broker networks to integrate<br/>for example geographically different data centres.</p>
+                    <h2 id="IntroducingActiveMQ">Introducing ActiveMQ</h2><p>Apache ActiveMQ is the most popular and powerful open source messaging and Integration Patterns provider.<br/>Apache ActiveMQ is fast, supports many Cross Language Clients and Protocols<br/>and many advanced features while fully supporting JMS 1.1 and J2EE 1.4. Apache ActiveMQ is released under the Apache 2.0 License</p><h3 id="ActiveMQSupports">ActiveMQ Supports</h3><h4 id="EasycommunicationviaCrossLanguageClients">Easy communication via Cross Language Clients</h4><ul><li><p>ActiveMQ C++ Clients</p></li><li><p>Ajax</p></li><li><p>C Integration</p></li><li><p>CMS</p></li><li><p>Delphi and FreePascal</p></li><li><p>dot Net</p></li><li><p>Perl</p></li><li><p>PHP</p></li><li><p>Pike</p></li><li><p>Python</p></li><li><p>Ruby</p></li><li><p>WebSockets</p></li><li><p>JMS to JMS Bridge</p></li></ul><h4 id="SeveralProtocols">Several Protocols</h4><ul><li><p>AMQP</p></li><li><p>OpenWire</p></li><li><p>REST</
 p></li><li><p>RSS and Atom</p></li><li><p>Stomp</p></li><li><p>WSIF</p></li><li><p>WS Notification</p></li><li><p>XMPP</p></li></ul><h3 id="UsingActiveMQfromServiceMix">Using ActiveMQ from ServiceMix</h3><p>To start using ActiveMQ from your code, simply get a hold of the connection pool declared in the activemq-broker.xml file.<br/>If you want to use ActiveMQ as a JBI component, configure servicemix-jms. You can also utilize ActiveMQ from Camel via the<br/>camel-jms component.</p><h3 id="WhenshouldIuseActiveMQ">When should I use ActiveMQ?</h3><p>Whenever you have a unit of work or payload that you could process asynchronously, you would like to have multiple recipients,<br/>concurrent competing recipients to scale or leverage multiple processing units. If you want to spread load across multiple<br/>system boundaries. You want to cluster or provide fail over and messaging security, you have long running flows.</p><p>In any of these instances it would be strongly suggested you
  evaluate what a scalable and secure messaging solution can bring to the table.</p><h3 id="Commonusecases">Common use cases</h3><p>Integration with other systems, since you can pass messages in and out of ActiveMQ from pretty much any programming language<br/>it is very simple to start integrating heterogeneous environments.</p><p>Providing an event driven architecture. You can develop your solutions based on actions as opposed to looking for data or<br/>relying on completely synchronous behaviour.</p><p>Providing infrastructure for messaging across large distances, leverage the network connectors and broker networks to integrate<br/>for example geographically different data centres.</p>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
Files servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf (original) and servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf Fri Feb  8 20:35:02 2013 differ

Modified: servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf.html (original)
+++ servicemix/site/production/docs/4.4.x/camel/camel-guide.pdf.html Fri Feb  8 20:35:02 2013
@@ -16,7 +16,7 @@
     </div>
   </div>
   <div id="main">
-    <h1 id="Introduction">Introduction</h1><p>Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration.</p><h2 id="CamelinServiceMix">Camel in ServiceMix</h2><p>In ServiceMix, Apache Camel is like our swiss army knife for creating integration solutions.  It allows using XML or a Java/Scala-based DSL to express your routes, comes with over 70 optional components, has powerful and versatile Java bean integration, error handling, ... and tons of other features.</p><p>Apache Camel is installed by default if you first start the container.  We also have out-of-the-box hot-deployment support for both Spring and Blueprint to make it easy to deploy your own Camel routes, as well as optionally installable features for all the available Camel components.</p><h2 id="Goalofthisguide">Goal of this guide</h2><p>The goal of this guide is to look into the details for using Camel inside ServiceMix:</p><ul><li>de
 ployment options</li><li>installing additional components</li></ul><h2 id="Examples">Examples</h2><p>The Apache ServiceMix distributions also contain a set of Camel examples.  You can find these examples in the <tt>examples/camel</tt> directory.</p><h2 id="MoreinformationaboutCamel">More information about Camel</h2><p>More information about Camel itself, can be found on <a href="http://camel.apache.org">http://camel.apache.org</a>.</p><p>There's also a great book available about Camel</p><ul><li>Ibsen, Claus, and Anstey, Jonathan. (December 2010). <em>Camel in Action</em>. Greenwich, CT: Manning. ISBN: 9781935182368.</li></ul><p><img border="0" src="http://www.manning.com/ibsen/ibsen_cover150.jpg"/></p><h1 id="Deploymentoptions">Deployment options</h1><p>There are a few different ways to deploy Camel routes on ServiceMix 4.4.2:</p><ul><li>deploy routes in a plain Blueprint XML file</li><li>deploy routes in a plain Spring XML file</li><li>deploy a bundle containing a Blueprin
 t XML file</li><li>deploy a bundle containing a Spring XML file</li></ul><p>Camel routes can also be deployed as part of a JBI SA, allowing you use Camel for routing between JBI endpoints - this option will be discussed later when we are talking about using JBI inside ServiceMix 4.</p><h3 id="Benefitsanddrawbacks">Benefits and drawbacks</h3><h4 id="PlainXMLorOSGibundles">Plain XML or OSGi bundles</h4><p>Choose a plain XML file:</p><ul><li>if you want to get routes deployed as quickly as possible <br/> all you need for developing routes is a simple text editor, no compilation, building, ... required at all</li><li>if you prefer the XML syntax over the Java of Scala DSL</li></ul><p>Choose an OSGi bundle:</p><ul><li>if you want to package helper classes together with your route definitions</li><li>if you prefer developing routes in the Java or Scala DSL <br/> you can package the RouteBuilder implementations inside the bundle</li></ul><h4 id="BlueprintorSpring">Blueprint or Spri
 ng</h4><p>Choose Blueprint:</p><ul><li>if you want the best possible integration with the OSGi Framework and Service Registy <br/> the Blueprint specification has been developed specifically for the OSGi Framework by the OSGi Alliance</li></ul><p>Choose Spring:</p><ul><li>if you already invested in Spring for creating and running Camel routes</li></ul><h2 id="DeployasaplainSpringXMLfile">Deploy as a plain Spring XML file</h2><p>ServiceMix 4.4.2 supports the deployment of plain Spring XML files, automatically creating and starting the Spring ApplicationContext from the XML file.</p><p>In order to leverage this feature to create and start Camel routes, drop a file with this syntax in the <tt>$SERVICEMIX_HOME/deploy</tt> folder:</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;beans</span> <span class="na">xmlns=</span><span class="s">&quot;http://www.springfra
 mework.org/schema/beans&quot;</span>&#x000A;       <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;       <span class="na">xmlns:camel=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span>&#x000A;       <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">          http://www.springframework.org/schema/beans</span>&#x000A;<span class="s">            http://www.springframework.org/schema/beans/spring-beans-2.5.xsd</span>&#x000A;<span class="s">          http://camel.apache.org/schema/spring</span>&#x000A;<span class="s">            http://camel.apache.org/schema/spring/camel-spring-2.8.5.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;  <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span><span class="nt">&gt;</span>&#x000A;    <span class
 ="c">&lt;!-- add Camel routes, interceptors,... here --&gt;</span> &#x000A;  <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/beans&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Anexample">An example</h3><p>Just create a new XML file in the deploy folder with the code below to start a route to copy files from one directory to another.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;beans</span> <span class="na">xmlns=</span><span class="s">&quot;http://www.springframework.org/schema/beans&quot;</span>&#x000A;       <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;       <span class="na">xmlns:camel=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span>&#x000A;       <span class="na">xsi:schemaLocation=</span><span class="s">&
 quot;</span>&#x000A;<span class="s">          http://www.springframework.org/schema/beans</span>&#x000A;<span class="s">            http://www.springframework.org/schema/beans/spring-beans-2.5.xsd</span>&#x000A;<span class="s">          http://camel.apache.org/schema/spring</span>&#x000A;<span class="s">            http://camel.apache.org/schema/spring/camel-spring-2.8.5.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;  <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span><span class="nt">&gt;</span>&#x000A;    <span class="nt">&lt;route&gt;</span>&#x000A;      <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;file:input&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;log</span> <span class="na">message=</span><span class="s">&quot;Copying ${file:name} to the output directory&quot;</span><span class="nt">/&gt;</spa
 n>&#x000A;      <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;file:output&quot;</span><span class="nt">/&gt;</span>&#x000A;    <span class="nt">&lt;/route&gt;</span>&#x000A;  <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/beans&gt;</span>&#x000A;</pre></div>&#x000A;</div><h2 id="DeployasaplainBlueprintXMLfile">Deploy as a plain Blueprint XML file</h2><p>ServiceMix 4.4.2 supports the deployment of plain Blueprint XML files, automatically creating and starting the Blueprint container from the XML file.</p><p>In order to leverage this feature to create and start Camel routes, drop a file with this syntax in the <tt>$SERVICEMIX_HOME/deploy</tt> folder:</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.os
 gi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;        <span class="c">&lt;!-- add Camel routes, interceptors,... here --&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Anexample">An example</h3><p>Just create a new XML file in the deploy folder with the code 
 below to start a route to copy files from one directory to another.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;    
   <span class="nt">&lt;route&gt;</span>&#x000A;        <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;file:input&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;log</span> <span class="na">message=</span><span class="s">&quot;Copying ${file:name} to the output directory&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;file:output&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;/route&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h2 id="DeployasanOSGibundlewithSpring">Deploy as an OSGi bundle with Spring</h2><p>Using an OSGi bundle to deploy your Camel routes allows you to use the Java or Scala DSL for defining your routes.</p><p>In this case, you're using Spring to start your Camel r
 outes, so you include your Spring XML file (e.g. <tt>camel-context.xml</tt>) in the <tt>META-INF/spring</tt> folder inside your bundle.</p><div class="syntax"><div class="highlight"><pre>+ &lt;bundle classes, incl. your RouteBuilder&gt;&#x000A;\- META-INF&#x000A;   |- MANIFEST.MF&#x000A;   \- spring&#x000A;      \- camel-context.xml&#x000A;</pre></div>&#x000A;</div><p>After the bundle has been activated, the Spring DM extender will find, create and start your Spring ApplicationContexts.</p><h3 id="ExampleReferringtoJavaorScalaRouteBuilderclasses">Example: Referring to Java or Scala RouteBuilder classes</h3><p>If your RouteBuilder classes have been defined in the <tt>org.apache.servicemix.manual.camel</tt> package, the file would look like this:</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;beans</span> <span class="na">xmlns=</span><span class="s">&quot;h
 ttp://www.springframework.org/schema/beans&quot;</span>&#x000A;       <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;       <span class="na">xmlns:camel=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span>&#x000A;       <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">          http://www.springframework.org/schema/beans</span>&#x000A;<span class="s">            http://www.springframework.org/schema/beans/spring-beans-2.5.xsd</span>&#x000A;<span class="s">          http://camel.apache.org/schema/spring</span>&#x000A;<span class="s">            http://camel.apache.org/schema/spring/camel-spring-${camel-version}.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;  <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span><span class="nt">&gt;
 </span>&#x000A;    <span class="nt">&lt;package&gt;</span>org.apache.servicemix.manual.camel<span class="nt">&lt;/package&gt;</span>&#x000A;  <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/beans&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Exampleinthedistribution">Example in the distribution</h3><p>Another example for using this deployment option can be found in the <tt>camel-osgi</tt> example that is shipped with Apache ServiceMix.</p><h2 id="DeployasanOSGibundle">Deploy as an OSGi bundle</h2><p>Using an OSGi bundle to deploy your Camel routes allows you to use the Java or Scala DSL for defining your routes.</p><p>In this case, we will use a Blueprint XML file to start your Camel routs.  To do so, the Blueprint XML files have to be included in the bundle inside the <tt>OSGI-INF/blueprint</tt> directory.</p><div class="syntax"><div class="highlight"><pre>+ &lt;bundle classes, incl. your RouteBuilder&gt;&#x000A;|- META-INF&#x000A;| 
  |- MANIFEST.MF&#x000A;\- OSGI-INF&#x000A;   \- blueprint&#x000A;      \- camel-context.xml&#x000A;</pre></div>&#x000A;</div><p>As soon as the bundle becomes Active, the Blueprint extender will create the Blueprint container starting your Routes.</p><h3 id="ExampleReferringtoJavaorScalaRouteBuilderclasses">Example: Referring to Java or Scala RouteBuilder classes</h3><p>If your RouteBuilder classes have been defined in the <tt>org.apache.servicemix.manual.camel</tt> package, the file would look like this:</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span
 ><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span class="nt">&lt;package&gt;</span>org.apache.servicemix.manual.camel<span class="nt">&lt;/package&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Exampleinthedistribution">Example in the distribution</h3><p>Another example for using this deployment option can be found in the <tt>camel-blueprint</tt> example that is shipped with Apache ServiceMix.</p><h1 id="Installingcomponents">Installing components</h1><p>Camel come
 s with over 80 components, so you can imagine that we don't install all of them by default.  This section shows you how to find available components and how to install them at runtime.</p><h3 id="Listavailablecomponents">List available components</h3><p>Camel components are available as installable features.  You can look at the full list of available features using the <tt>features:list</tt> command, using <tt>grep</tt> to limit things down to features related to camel:</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:list | grep camel&#x000A;[installed  ] [2.8.5    ] camel                                repo-0&#x000A;[installed  ] [2.8.5    ] camel-core                           repo-0&#x000A;[installed  ] [2.8.5    ] camel-spring                         repo-0&#x000A;[installed  ] [2.8.5    ] camel-blueprint                      repo-0&#x000A;[uninstalled] [2.8.5    ] camel-test                           repo-0&#x000A;[uninstalled] [2.8.5    ] ca
 mel-cxf                            repo-0&#x000A;[uninstalled] [2.8.5    ] camel-cache                          repo-0&#x000A;[uninstalled] [2.8.5    ] camel-castor                         repo-0&#x000A;...&#x000A;</pre></div>&#x000A;</div><p>The items marked with <strong><tt>installed</tt></strong> in the first column have already been installed and are available for use in your Camel routes.</p><h3 id="Installanduninstallingcomponents">Install and uninstalling components</h3><p>You can use <tt>features:install</tt> to install any component on the list.</p><p>An example: to install the <tt>camel-cache</tt> component</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:install camel-cache&#x000A;</pre></div>&#x000A;</div><p>Similarly, you can also uninstall components that you're no longer using with <tt>features:uninstall</tt></p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:uninstall camel-cache&#x000A;{pygementize}&#x000A;</
 pre></div>&#x000A;</div><h1 id="Troubleshooting">Troubleshooting</h1><p>In this section, you'll find solutions for some frequently asked questions when using Camel on ServicMix.</p><h3 id="Nocomponentwithidxyzcouldbefound">No component with id 'xyz' could be found</h3><p>This usually means that your route is trying to use a component that hasn't been installed yet.</p><p>Solution:</p><ol><li>install the additional component</li><li>restart the bundle using the <tt>osg:restart &lt;bundle id></tt> command - you can find the bundle id for your route in the output of the <tt>osgi:list</tt> command</li></ol><p>Refer to <a href="../users-guide/camel/installing-components.html">Installing additional components</a> for more information about installing additional components.</p>
+    <h1 id="Introduction">Introduction</h1><p>Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration.</p><h2 id="CamelinServiceMix">Camel in ServiceMix</h2><p>In ServiceMix, Apache Camel is like our swiss army knife for creating integration solutions.  It allows using XML or a Java/Scala-based DSL to express your routes, comes with over 70 optional components, has powerful and versatile Java bean integration, error handling, ... and tons of other features.</p><p>Apache Camel is installed by default if you first start the container.  We also have out-of-the-box hot-deployment support for both Spring and Blueprint to make it easy to deploy your own Camel routes, as well as optionally installable features for all the available Camel components.</p><h2 id="Goalofthisguide">Goal of this guide</h2><p>The goal of this guide is to look into the details for using Camel inside ServiceMix:</p><ul><li><p
 >deployment options</p></li><li><p>installing additional components</p></li></ul><h2 id="Examples">Examples</h2><p>The Apache ServiceMix distributions also contain a set of Camel examples.  You can find these examples in the <tt>examples/camel</tt> directory.</p><h2 id="MoreinformationaboutCamel">More information about Camel</h2><p>More information about Camel itself, can be found on <a href="http://camel.apache.org">http://camel.apache.org</a>.</p><p>There's also a great book available about Camel</p><ul><li><p>Ibsen, Claus, and Anstey, Jonathan. (December 2010). <em>Camel in Action</em>. Greenwich, CT: Manning. ISBN: 9781935182368.</p></li></ul><p><img border="0" src="http://www.manning.com/ibsen/ibsen_cover150.jpg"/></p><h1 id="Deploymentoptions">Deployment options</h1><p>There are a few different ways to deploy Camel routes on ServiceMix 4.4.2:</p><ul><li><p>deploy routes in a plain Blueprint XML file</p></li><li><p>deploy routes in a plain Spring XML file</p></li><li><p
 >deploy a bundle containing a Blueprint XML file</p></li><li><p>deploy a bundle containing a Spring XML file</p></li></ul><p>Camel routes can also be deployed as part of a JBI SA, allowing you use Camel for routing between JBI endpoints - this option will be discussed later when we are talking about using JBI inside ServiceMix 4.</p><h3 id="Benefitsanddrawbacks">Benefits and drawbacks</h3><h4 id="PlainXMLorOSGibundles">Plain XML or OSGi bundles</h4><p>Choose a plain XML file:</p><ul><li><p>if you want to get routes deployed as quickly as possible <br/> all you need for developing routes is a simple text editor, no compilation, building, ... required at all</p></li><li><p>if you prefer the XML syntax over the Java of Scala DSL</p></li></ul><p>Choose an OSGi bundle:</p><ul><li><p>if you want to package helper classes together with your route definitions</p></li><li><p>if you prefer developing routes in the Java or Scala DSL <br/> you can package the RouteBuilder implementation
 s inside the bundle</p></li></ul><h4 id="BlueprintorSpring">Blueprint or Spring</h4><p>Choose Blueprint:</p><ul><li><p>if you want the best possible integration with the OSGi Framework and Service Registy <br/> the Blueprint specification has been developed specifically for the OSGi Framework by the OSGi Alliance</p></li></ul><p>Choose Spring:</p><ul><li><p>if you already invested in Spring for creating and running Camel routes</p></li></ul><h2 id="DeployasaplainSpringXMLfile">Deploy as a plain Spring XML file</h2><p>ServiceMix 4.4.2 supports the deployment of plain Spring XML files, automatically creating and starting the Spring ApplicationContext from the XML file.</p><p>In order to leverage this feature to create and start Camel routes, drop a file with this syntax in the <tt>$SERVICEMIX_HOME/deploy</tt> folder:</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt
 ">&lt;beans</span> <span class="na">xmlns=</span><span class="s">&quot;http://www.springframework.org/schema/beans&quot;</span>&#x000A;       <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;       <span class="na">xmlns:camel=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span>&#x000A;       <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">          http://www.springframework.org/schema/beans</span>&#x000A;<span class="s">            http://www.springframework.org/schema/beans/spring-beans-2.5.xsd</span>&#x000A;<span class="s">          http://camel.apache.org/schema/spring</span>&#x000A;<span class="s">            http://camel.apache.org/schema/spring/camel-spring-2.8.5.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;  <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://cam
 el.apache.org/schema/spring&quot;</span><span class="nt">&gt;</span>&#x000A;    <span class="c">&lt;!-- add Camel routes, interceptors,... here --&gt;</span> &#x000A;  <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/beans&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Anexample">An example</h3><p>Just create a new XML file in the deploy folder with the code below to start a route to copy files from one directory to another.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;beans</span> <span class="na">xmlns=</span><span class="s">&quot;http://www.springframework.org/schema/beans&quot;</span>&#x000A;       <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;       <span class="na">xmlns:camel=</span><span class="s">&quot;http://camel.apache.org/schema/spr
 ing&quot;</span>&#x000A;       <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">          http://www.springframework.org/schema/beans</span>&#x000A;<span class="s">            http://www.springframework.org/schema/beans/spring-beans-2.5.xsd</span>&#x000A;<span class="s">          http://camel.apache.org/schema/spring</span>&#x000A;<span class="s">            http://camel.apache.org/schema/spring/camel-spring-2.8.5.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;  <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span><span class="nt">&gt;</span>&#x000A;    <span class="nt">&lt;route&gt;</span>&#x000A;      <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;file:input&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;log</span> <span class="na">message=</span><span class="s"
 >&quot;Copying ${file:name} to the output directory&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;file:output&quot;</span><span class="nt">/&gt;</span>&#x000A;    <span class="nt">&lt;/route&gt;</span>&#x000A;  <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/beans&gt;</span>&#x000A;</pre></div>&#x000A;</div><h2 id="DeployasaplainBlueprintXMLfile">Deploy as a plain Blueprint XML file</h2><p>ServiceMix 4.4.2 supports the deployment of plain Blueprint XML files, automatically creating and starting the Blueprint container from the XML file.</p><p>In order to leverage this feature to create and start Camel routes, drop a file with this syntax in the <tt>$SERVICEMIX_HOME/deploy</tt> folder:</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;bl
 ueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;        <span class="c">&lt;!-- add Camel routes, interceptors,... here --&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="
 Anexample">An example</h3><p>Just create a new XML file in the deploy folder with the code below to start a route to copy files from one directory to another.</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;ht
 tp://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span class="nt">&lt;route&gt;</span>&#x000A;        <span class="nt">&lt;from</span> <span class="na">uri=</span><span class="s">&quot;file:input&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;log</span> <span class="na">message=</span><span class="s">&quot;Copying ${file:name} to the output directory&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;file:output&quot;</span><span class="nt">/&gt;</span>&#x000A;      <span class="nt">&lt;/route&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h2 id="DeployasanOSGibundlewithSpring">Deploy as an OSGi bundle with Spring</h2><p>Using an OSGi bundle to deploy your Camel routes allows you to use the Java or Scala 
 DSL for defining your routes.</p><p>In this case, you're using Spring to start your Camel routes, so you include your Spring XML file (e.g. <tt>camel-context.xml</tt>) in the <tt>META-INF/spring</tt> folder inside your bundle.</p><div class="syntax"><div class="highlight"><pre>+ &lt;bundle classes, incl. your RouteBuilder&gt;&#x000A;\- META-INF&#x000A;   |- MANIFEST.MF&#x000A;   \- spring&#x000A;      \- camel-context.xml&#x000A;</pre></div>&#x000A;</div><p>After the bundle has been activated, the Spring DM extender will find, create and start your Spring ApplicationContexts.</p><h3 id="ExampleReferringtoJavaorScalaRouteBuilderclasses">Example: Referring to Java or Scala RouteBuilder classes</h3><p>If your RouteBuilder classes have been defined in the <tt>org.apache.servicemix.manual.camel</tt> package, the file would look like this:</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x0
 00A;<span class="nt">&lt;beans</span> <span class="na">xmlns=</span><span class="s">&quot;http://www.springframework.org/schema/beans&quot;</span>&#x000A;       <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span>&#x000A;       <span class="na">xmlns:camel=</span><span class="s">&quot;http://camel.apache.org/schema/spring&quot;</span>&#x000A;       <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">          http://www.springframework.org/schema/beans</span>&#x000A;<span class="s">            http://www.springframework.org/schema/beans/spring-beans-2.5.xsd</span>&#x000A;<span class="s">          http://camel.apache.org/schema/spring</span>&#x000A;<span class="s">            http://camel.apache.org/schema/spring/camel-spring-${camel-version}.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;  <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><s
 pan class="s">&quot;http://camel.apache.org/schema/spring&quot;</span><span class="nt">&gt;</span>&#x000A;    <span class="nt">&lt;package&gt;</span>org.apache.servicemix.manual.camel<span class="nt">&lt;/package&gt;</span>&#x000A;  <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/beans&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Exampleinthedistribution">Example in the distribution</h3><p>Another example for using this deployment option can be found in the <tt>camel-osgi</tt> example that is shipped with Apache ServiceMix.</p><h2 id="DeployasanOSGibundle">Deploy as an OSGi bundle</h2><p>Using an OSGi bundle to deploy your Camel routes allows you to use the Java or Scala DSL for defining your routes.</p><p>In this case, we will use a Blueprint XML file to start your Camel routs.  To do so, the Blueprint XML files have to be included in the bundle inside the <tt>OSGI-INF/blueprint</tt> directory.</p><div class="syntax"><div class="hig
 hlight"><pre>+ &lt;bundle classes, incl. your RouteBuilder&gt;&#x000A;|- META-INF&#x000A;|  |- MANIFEST.MF&#x000A;\- OSGI-INF&#x000A;   \- blueprint&#x000A;      \- camel-context.xml&#x000A;</pre></div>&#x000A;</div><p>As soon as the bundle becomes Active, the Blueprint extender will create the Blueprint container starting your Routes.</p><h3 id="ExampleReferringtoJavaorScalaRouteBuilderclasses">Example: Referring to Java or Scala RouteBuilder classes</h3><p>If your RouteBuilder classes have been defined in the <tt>org.apache.servicemix.manual.camel</tt> package, the file would look like this:</p><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;</span>&#x000A;<span class="nt">&lt;blueprint</span>&#x000A;    <span class="na">xmlns=</span><span class="s">&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;</span>&#x000A;    <span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org
 /2001/XMLSchema-instance&quot;</span>&#x000A;    <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0</span>&#x000A;<span class="s">      http://www.osgi.org/xmlns/blueprint/v1.0.0/blueprint.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">xmlns=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;      <span class="nt">&lt;package&gt;</span>org.apache.servicemix.manual.camel<span class="nt">&lt;/package&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Exampleinthedistribution">Example in the distribution</h3><p>Another example for using this deployment option can be found in the <tt>camel-blueprint</tt> example that is shipped with 
 Apache ServiceMix.</p><h1 id="Installingcomponents">Installing components</h1><p>Camel comes with over 80 components, so you can imagine that we don't install all of them by default.  This section shows you how to find available components and how to install them at runtime.</p><h3 id="Listavailablecomponents">List available components</h3><p>Camel components are available as installable features.  You can look at the full list of available features using the <tt>features:list</tt> command, using <tt>grep</tt> to limit things down to features related to camel:</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:list | grep camel&#x000A;[installed  ] [2.8.5    ] camel                                repo-0&#x000A;[installed  ] [2.8.5    ] camel-core                           repo-0&#x000A;[installed  ] [2.8.5    ] camel-spring                         repo-0&#x000A;[installed  ] [2.8.5    ] camel-blueprint                      repo-0&#x000A;[uninstalled] 
 [2.8.5    ] camel-test                           repo-0&#x000A;[uninstalled] [2.8.5    ] camel-cxf                            repo-0&#x000A;[uninstalled] [2.8.5    ] camel-cache                          repo-0&#x000A;[uninstalled] [2.8.5    ] camel-castor                         repo-0&#x000A;...&#x000A;</pre></div>&#x000A;</div><p>The items marked with <strong><tt>installed</tt></strong> in the first column have already been installed and are available for use in your Camel routes.</p><h3 id="Installanduninstallingcomponents">Install and uninstalling components</h3><p>You can use <tt>features:install</tt> to install any component on the list.</p><p>An example: to install the <tt>camel-cache</tt> component</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt; features:install camel-cache&#x000A;</pre></div>&#x000A;</div><p>Similarly, you can also uninstall components that you're no longer using with <tt>features:uninstall</tt></p><div class="syntax"><div class="h
 ighlight"><pre>karaf@root&gt; features:uninstall camel-cache&#x000A;{pygementize}&#x000A;</pre></div>&#x000A;</div><h1 id="Troubleshooting">Troubleshooting</h1><p>In this section, you'll find solutions for some frequently asked questions when using Camel on ServicMix.</p><h3 id="Nocomponentwithidxyzcouldbefound">No component with id 'xyz' could be found</h3><p>This usually means that your route is trying to use a component that hasn't been installed yet.</p><p>Solution:</p><ol><li><p>install the additional component</p></li><li><p>restart the bundle using the <tt>osg:restart &lt;bundle id></tt> command - you can find the bundle id for your route in the output of the <tt>osgi:list</tt> command</p></li></ol><p>Refer to <a href="../users-guide/camel/installing-components.html">Installing additional components</a> for more information about installing additional components.</p>
   </div>
 </body>
 </html>
\ No newline at end of file

Modified: servicemix/site/production/docs/4.4.x/camel/deployment/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/camel/deployment/index.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/camel/deployment/index.html (original)
+++ servicemix/site/production/docs/4.4.x/camel/deployment/index.html Fri Feb  8 20:35:02 2013
@@ -90,7 +90,7 @@
 </ul>
         </div>
         <div id="body">
-                    <p>There are a few different ways to deploy Camel routes on ServiceMix 4.4.2:</p><ul><li>deploy routes in a plain Blueprint XML file</li><li>deploy routes in a plain Spring XML file</li><li>deploy a bundle containing a Blueprint XML file</li><li>deploy a bundle containing a Spring XML file</li></ul><p>Camel routes can also be deployed as part of a JBI SA, allowing you use Camel for routing between JBI endpoints - this option will be discussed later when we are talking about using JBI inside ServiceMix 4.</p><h3 id="Benefitsanddrawbacks">Benefits and drawbacks</h3><h4 id="PlainXMLorOSGibundles">Plain XML or OSGi bundles</h4><p>Choose a plain XML file:</p><ul><li>if you want to get routes deployed as quickly as possible <br/> all you need for developing routes is a simple text editor, no compilation, building, ... required at all</li><li>if you prefer the XML syntax over the Java of Scala DSL</li></ul><p>Choose an OSGi bundle:</p><ul><li>if you want to pack
 age helper classes together with your route definitions</li><li>if you prefer developing routes in the Java or Scala DSL <br/> you can package the RouteBuilder implementations inside the bundle</li></ul><h4 id="BlueprintorSpring">Blueprint or Spring</h4><p>Choose Blueprint:</p><ul><li>if you want the best possible integration with the OSGi Framework and Service Registy <br/> the Blueprint specification has been developed specifically for the OSGi Framework by the OSGi Alliance</li></ul><p>Choose Spring:</p><ul><li>if you already invested in Spring for creating and running Camel routes</li></ul>
+                    <p>There are a few different ways to deploy Camel routes on ServiceMix 4.4.2:</p><ul><li><p>deploy routes in a plain Blueprint XML file</p></li><li><p>deploy routes in a plain Spring XML file</p></li><li><p>deploy a bundle containing a Blueprint XML file</p></li><li><p>deploy a bundle containing a Spring XML file</p></li></ul><p>Camel routes can also be deployed as part of a JBI SA, allowing you use Camel for routing between JBI endpoints - this option will be discussed later when we are talking about using JBI inside ServiceMix 4.</p><h3 id="Benefitsanddrawbacks">Benefits and drawbacks</h3><h4 id="PlainXMLorOSGibundles">Plain XML or OSGi bundles</h4><p>Choose a plain XML file:</p><ul><li><p>if you want to get routes deployed as quickly as possible <br/> all you need for developing routes is a simple text editor, no compilation, building, ... required at all</p></li><li><p>if you prefer the XML syntax over the Java of Scala DSL</p></li></ul><p>Choose an O
 SGi bundle:</p><ul><li><p>if you want to package helper classes together with your route definitions</p></li><li><p>if you prefer developing routes in the Java or Scala DSL <br/> you can package the RouteBuilder implementations inside the bundle</p></li></ul><h4 id="BlueprintorSpring">Blueprint or Spring</h4><p>Choose Blueprint:</p><ul><li><p>if you want the best possible integration with the OSGi Framework and Service Registy <br/> the Blueprint specification has been developed specifically for the OSGi Framework by the OSGi Alliance</p></li></ul><p>Choose Spring:</p><ul><li><p>if you already invested in Spring for creating and running Camel routes</p></li></ul>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/camel/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/camel/index.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/camel/index.html (original)
+++ servicemix/site/production/docs/4.4.x/camel/index.html Fri Feb  8 20:35:02 2013
@@ -90,7 +90,7 @@
 </ul>
         </div>
         <div id="body">
-                    <p>Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration.</p><h2 id="CamelinServiceMix">Camel in ServiceMix</h2><p>In ServiceMix, Apache Camel is like our swiss army knife for creating integration solutions.  It allows using XML or a Java/Scala-based DSL to express your routes, comes with over 70 optional components, has powerful and versatile Java bean integration, error handling, ... and tons of other features.</p><p>Apache Camel is installed by default if you first start the container.  We also have out-of-the-box hot-deployment support for both Spring and Blueprint to make it easy to deploy your own Camel routes, as well as optionally installable features for all the available Camel components.</p><h2 id="Goalofthisguide">Goal of this guide</h2><p>The goal of this guide is to look into the details for using Camel inside ServiceMix:</p><ul><li>deployment options</li><l
 i>installing additional components</li></ul><h2 id="Examples">Examples</h2><p>The Apache ServiceMix distributions also contain a set of Camel examples.  You can find these examples in the <tt>examples/camel</tt> directory.</p><h2 id="MoreinformationaboutCamel">More information about Camel</h2><p>More information about Camel itself, can be found on <a href="http://camel.apache.org">http://camel.apache.org</a>.</p><p>There's also a great book available about Camel</p><ul><li>Ibsen, Claus, and Anstey, Jonathan. (December 2010). <em>Camel in Action</em>. Greenwich, CT: Manning. ISBN: 9781935182368.</li></ul><p><img border="0" src="http://www.manning.com/ibsen/ibsen_cover150.jpg"/></p>
+                    <p>Apache Camel is a powerful open source integration framework based on known Enterprise Integration Patterns with powerful Bean Integration.</p><h2 id="CamelinServiceMix">Camel in ServiceMix</h2><p>In ServiceMix, Apache Camel is like our swiss army knife for creating integration solutions.  It allows using XML or a Java/Scala-based DSL to express your routes, comes with over 70 optional components, has powerful and versatile Java bean integration, error handling, ... and tons of other features.</p><p>Apache Camel is installed by default if you first start the container.  We also have out-of-the-box hot-deployment support for both Spring and Blueprint to make it easy to deploy your own Camel routes, as well as optionally installable features for all the available Camel components.</p><h2 id="Goalofthisguide">Goal of this guide</h2><p>The goal of this guide is to look into the details for using Camel inside ServiceMix:</p><ul><li><p>deployment options</p>
 </li><li><p>installing additional components</p></li></ul><h2 id="Examples">Examples</h2><p>The Apache ServiceMix distributions also contain a set of Camel examples.  You can find these examples in the <tt>examples/camel</tt> directory.</p><h2 id="MoreinformationaboutCamel">More information about Camel</h2><p>More information about Camel itself, can be found on <a href="http://camel.apache.org">http://camel.apache.org</a>.</p><p>There's also a great book available about Camel</p><ul><li><p>Ibsen, Claus, and Anstey, Jonathan. (December 2010). <em>Camel in Action</em>. Greenwich, CT: Manning. ISBN: 9781935182368.</p></li></ul><p><img border="0" src="http://www.manning.com/ibsen/ibsen_cover150.jpg"/></p>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/camel/troubleshooting.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/camel/troubleshooting.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/camel/troubleshooting.html (original)
+++ servicemix/site/production/docs/4.4.x/camel/troubleshooting.html Fri Feb  8 20:35:02 2013
@@ -90,7 +90,7 @@
 </ul>
         </div>
         <div id="body">
-                    <p>In this section, you'll find solutions for some frequently asked questions when using Camel on ServicMix.</p><h3 id="Nocomponentwithidxyzcouldbefound">No component with id 'xyz' could be found</h3><p>This usually means that your route is trying to use a component that hasn't been installed yet.</p><p>Solution:</p><ol><li>install the additional component</li><li>restart the bundle using the <tt>osg:restart &lt;bundle id></tt> command - you can find the bundle id for your route in the output of the <tt>osgi:list</tt> command</li></ol><p>Refer to <a href="../users-guide/camel/installing-components.html">Installing additional components</a> for more information about installing additional components.</p>
+                    <p>In this section, you'll find solutions for some frequently asked questions when using Camel on ServicMix.</p><h3 id="Nocomponentwithidxyzcouldbefound">No component with id 'xyz' could be found</h3><p>This usually means that your route is trying to use a component that hasn't been installed yet.</p><p>Solution:</p><ol><li><p>install the additional component</p></li><li><p>restart the bundle using the <tt>osg:restart &lt;bundle id></tt> command - you can find the bundle id for your route in the output of the <tt>osgi:list</tt> command</p></li></ol><p>Refer to <a href="../users-guide/camel/installing-components.html">Installing additional components</a> for more information about installing additional components.</p>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/commands/admin-change-opts.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/commands/admin-change-opts.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/commands/admin-change-opts.html (original)
+++ servicemix/site/production/docs/4.4.x/commands/admin-change-opts.html Fri Feb  8 20:35:02 2013
@@ -138,7 +138,7 @@
 </ul>
         </div>
         <div id="body">
-                    <h1 id="adminchangeopts">admin:change-opts</h1><h2 id="Description">Description</h2><p>Changes the Java options of an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:change-opts \<a href="options.html">options\</a> name javaOpts </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> javaOpts </td><td class="confluenceTd"> The new Java options to set </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr></table></div>
+                    <h1 id="adminchangeopts">admin:change-opts</h1><h2 id="Description">Description</h2><p>Changes the Java options of an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:change-opts [options] name javaOpts </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> javaOpts </td><td class="confluenceTd"> The new Java options to set </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr></table></div>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-registry-port.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-registry-port.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-registry-port.html (original)
+++ servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-registry-port.html Fri Feb  8 20:35:02 2013
@@ -138,7 +138,7 @@
 </ul>
         </div>
         <div id="body">
-                    <h1 id="adminchangermiregistryport">admin:change-rmi-registry-port</h1><h2 id="Description">Description</h2><p>Changes the RMI registry port (used by management layer) of an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:change-rmi-registry-port \<a href="options.html">options\</a> name port </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> port </td><td class="confluenceTd"> The new RMI registry port to set </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> D
 isplay this help message </td></tr></table></div>
+                    <h1 id="adminchangermiregistryport">admin:change-rmi-registry-port</h1><h2 id="Description">Description</h2><p>Changes the RMI registry port (used by management layer) of an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:change-rmi-registry-port [options] name port </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> port </td><td class="confluenceTd"> The new RMI registry port to set </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </
 td></tr></table></div>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-server-port.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-server-port.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-server-port.html (original)
+++ servicemix/site/production/docs/4.4.x/commands/admin-change-rmi-server-port.html Fri Feb  8 20:35:02 2013
@@ -138,7 +138,7 @@
 </ul>
         </div>
         <div id="body">
-                    <h1 id="adminchangermiserverport">admin:change-rmi-server-port</h1><h2 id="Description">Description</h2><p>Changes the RMI server port (used by management layer) of an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:change-rmi-server-port \<a href="options.html">options\</a> name port </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> port </td><td class="confluenceTd"> The new RMI server port to set </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display thi
 s help message </td></tr></table></div>
+                    <h1 id="adminchangermiserverport">admin:change-rmi-server-port</h1><h2 id="Description">Description</h2><p>Changes the RMI server port (used by management layer) of an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:change-rmi-server-port [options] name port </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> port </td><td class="confluenceTd"> The new RMI server port to set </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr></
 table></div>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/commands/admin-change-ssh-port.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/commands/admin-change-ssh-port.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/commands/admin-change-ssh-port.html (original)
+++ servicemix/site/production/docs/4.4.x/commands/admin-change-ssh-port.html Fri Feb  8 20:35:02 2013
@@ -138,7 +138,7 @@
 </ul>
         </div>
         <div id="body">
-                    <h1 id="adminchangesshport">admin:change-ssh-port</h1><h2 id="Description">Description</h2><p>Changes the secure shell port of an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:change-ssh-port \<a href="options.html">options\</a> name port </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> port </td><td class="confluenceTd"> The new secure shell port to set </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr></table></div>
+                    <h1 id="adminchangesshport">admin:change-ssh-port</h1><h2 id="Description">Description</h2><p>Changes the secure shell port of an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:change-ssh-port [options] name port </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> port </td><td class="confluenceTd"> The new secure shell port to set </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr></table></div>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/commands/admin-connect.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/commands/admin-connect.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/commands/admin-connect.html (original)
+++ servicemix/site/production/docs/4.4.x/commands/admin-connect.html Fri Feb  8 20:35:02 2013
@@ -138,7 +138,7 @@
 </ul>
         </div>
         <div id="body">
-                    <h1 id="adminconnect">admin:connect</h1><h2 id="Description">Description</h2><p>Connects to an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:connect \<a href="options.html">options\</a> name \<a href="command.html">command\</a> </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> command </td><td class="confluenceTd"> Optional command to execute </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> <del>u, -</del>username </td><td class="confluenceTd"> Remote user name (Default: karaf) (defaults to kar
 af) </td></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr><tr><td class="confluenceTd"> <del>p, -</del>password </td><td class="confluenceTd"> Remote user password (Default: karaf) (defaults to karaf) </td></tr></table></div>
+                    <h1 id="adminconnect">admin:connect</h1><h2 id="Description">Description</h2><p>Connects to an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:connect [options] name [command] </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance </td></tr><tr><td class="confluenceTd"> command </td><td class="confluenceTd"> Optional command to execute </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> -u, --username </td><td class="confluenceTd"> Remote user name (Default: karaf) (defaults to karaf) </td></tr><tr><td class="confluenceTd"> --help </td><td cla
 ss="confluenceTd"> Display this help message </td></tr><tr><td class="confluenceTd"> -p, --password </td><td class="confluenceTd"> Remote user password (Default: karaf) (defaults to karaf) </td></tr></table></div>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/commands/admin-create.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/commands/admin-create.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/commands/admin-create.html (original)
+++ servicemix/site/production/docs/4.4.x/commands/admin-create.html Fri Feb  8 20:35:02 2013
@@ -138,7 +138,7 @@
 </ul>
         </div>
         <div id="body">
-                    <h1 id="admincreate">admin:create</h1><h2 id="Description">Description</h2><p>Creates a new container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:create \<a href="options.html">options\</a> name </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the new container instance </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr><tr><td class="confluenceTd"> <del>l, -</del>location </td><td class="confluenceTd"> Location of the new container instance in the file system </td></tr><tr><td class="confluenceTd"> <
 del>furl, -</del>featureURL </td><td class="confluenceTd"> Additional feature descriptor URLs. This option can be specified multiple times to add multiple URLs </td></tr><tr><td class="confluenceTd"> <del>f, -</del>feature </td><td class="confluenceTd"> Initial features. This option can be specified multiple times to enable multiple initial features </td></tr><tr><td class="confluenceTd"> <del>s, -</del>ssh-port </td><td class="confluenceTd"> Port number for remote secure shell connection </td></tr><tr><td class="confluenceTd"> <del>rs, -</del>rmi-server-port </td><td class="confluenceTd"> Port number for RMI server connection </td></tr><tr><td class="confluenceTd"> <del>o, -</del>java-opts </td><td class="confluenceTd"> JVM options to use when launching the instance </td></tr><tr><td class="confluenceTd"> <del>r, -rr, -</del>rmi-port, <del>-rmi</del>registry-port </td><td class="confluenceTd"> Port number for RMI registry connection </td></tr></table></div>
+                    <h1 id="admincreate">admin:create</h1><h2 id="Description">Description</h2><p>Creates a new container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:create [options] name </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the new container instance </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr><tr><td class="confluenceTd"> -l, --location </td><td class="confluenceTd"> Location of the new container instance in the file system </td></tr><tr><td class="confluenceTd"> -furl, --featureURL </td><td class="c
 onfluenceTd"> Additional feature descriptor URLs. This option can be specified multiple times to add multiple URLs </td></tr><tr><td class="confluenceTd"> -f, --feature </td><td class="confluenceTd"> Initial features. This option can be specified multiple times to enable multiple initial features </td></tr><tr><td class="confluenceTd"> -s, --ssh-port </td><td class="confluenceTd"> Port number for remote secure shell connection </td></tr><tr><td class="confluenceTd"> -rs, --rmi-server-port </td><td class="confluenceTd"> Port number for RMI server connection </td></tr><tr><td class="confluenceTd"> -o, --java-opts </td><td class="confluenceTd"> JVM options to use when launching the instance </td></tr><tr><td class="confluenceTd"> -r, -rr, --rmi-port, --rmi-registry-port </td><td class="confluenceTd"> Port number for RMI registry connection </td></tr></table></div>
         </div>
       
           </div>

Modified: servicemix/site/production/docs/4.4.x/commands/admin-destroy.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/4.4.x/commands/admin-destroy.html?rev=1444219&r1=1444218&r2=1444219&view=diff
==============================================================================
--- servicemix/site/production/docs/4.4.x/commands/admin-destroy.html (original)
+++ servicemix/site/production/docs/4.4.x/commands/admin-destroy.html Fri Feb  8 20:35:02 2013
@@ -138,7 +138,7 @@
 </ul>
         </div>
         <div id="body">
-                    <h1 id="admindestroy">admin:destroy</h1><h2 id="Description">Description</h2><p>Destroys an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:destroy \<a href="options.html">options\</a> name </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance to destroy </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr></table></div>
+                    <h1 id="admindestroy">admin:destroy</h1><h2 id="Description">Description</h2><p>Destroys an existing container instance.</p><h2 id="Syntax">Syntax</h2><p>admin:destroy [options] name </p><h2 id="Arguments">Arguments</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> name </td><td class="confluenceTd"> The name of the container instance to destroy </td></tr></table></div><h2 id="Options">Options</h2><div class="table-wrap"><table class="confluenceTable"><tr><th class="confluenceTh"> Name </th><th class="confluenceTh"> Description </th></tr><tr><td class="confluenceTd"> --help </td><td class="confluenceTd"> Display this help message </td></tr></table></div>
         </div>
       
           </div>