servicemix-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From ge...@apache.org
Subject svn commit: r1597941 [1/6] - in /servicemix/site/production/docs/5.0.x: ./ activemq/ activiti/ camel/ camel/deployment/ commands/ developers-guide/ karaf/ quickstart/ user/ users-guide/
Date Wed, 28 May 2014 08:20:18 GMT
Author: gertv
Date: Wed May 28 08:20:15 2014
New Revision: 1597941

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

Modified:
    servicemix/site/production/docs/5.0.x/activemq/activemq-camel-example.html
    servicemix/site/production/docs/5.0.x/activemq/index.html
    servicemix/site/production/docs/5.0.x/activemq/toc.html
    servicemix/site/production/docs/5.0.x/activiti/activiti-camel-example.html
    servicemix/site/production/docs/5.0.x/activiti/index.html
    servicemix/site/production/docs/5.0.x/activiti/toc.html
    servicemix/site/production/docs/5.0.x/camel/camel-guide.pdf.html
    servicemix/site/production/docs/5.0.x/camel/deployment/index.html
    servicemix/site/production/docs/5.0.x/camel/deployment/osgi-bundle-blueprint.html
    servicemix/site/production/docs/5.0.x/camel/deployment/osgi-bundle-spring.html
    servicemix/site/production/docs/5.0.x/camel/deployment/plain-blueprint.html
    servicemix/site/production/docs/5.0.x/camel/deployment/plain-spring.html
    servicemix/site/production/docs/5.0.x/camel/index.html
    servicemix/site/production/docs/5.0.x/camel/installing-components.html
    servicemix/site/production/docs/5.0.x/camel/toc.html
    servicemix/site/production/docs/5.0.x/camel/troubleshooting.html
    servicemix/site/production/docs/5.0.x/commands/admin-change-opts.html
    servicemix/site/production/docs/5.0.x/commands/admin-change-rmi-registry-port.html
    servicemix/site/production/docs/5.0.x/commands/admin-change-rmi-server-port.html
    servicemix/site/production/docs/5.0.x/commands/admin-change-ssh-port.html
    servicemix/site/production/docs/5.0.x/commands/admin-connect.html
    servicemix/site/production/docs/5.0.x/commands/admin-create.html
    servicemix/site/production/docs/5.0.x/commands/admin-destroy.html
    servicemix/site/production/docs/5.0.x/commands/admin-list.html
    servicemix/site/production/docs/5.0.x/commands/admin-rename.html
    servicemix/site/production/docs/5.0.x/commands/admin-start.html
    servicemix/site/production/docs/5.0.x/commands/admin-stop.html
    servicemix/site/production/docs/5.0.x/commands/commands.html
    servicemix/site/production/docs/5.0.x/commands/config-cancel.html
    servicemix/site/production/docs/5.0.x/commands/config-delete.html
    servicemix/site/production/docs/5.0.x/commands/config-edit.html
    servicemix/site/production/docs/5.0.x/commands/config-list.html
    servicemix/site/production/docs/5.0.x/commands/config-propappend.html
    servicemix/site/production/docs/5.0.x/commands/config-propdel.html
    servicemix/site/production/docs/5.0.x/commands/config-proplist.html
    servicemix/site/production/docs/5.0.x/commands/config-propset.html
    servicemix/site/production/docs/5.0.x/commands/config-update.html
    servicemix/site/production/docs/5.0.x/commands/dev-create-dump.html
    servicemix/site/production/docs/5.0.x/commands/dev-dynamic-import.html
    servicemix/site/production/docs/5.0.x/commands/dev-framework.html
    servicemix/site/production/docs/5.0.x/commands/dev-print-stack-traces.html
    servicemix/site/production/docs/5.0.x/commands/dev-restart.html
    servicemix/site/production/docs/5.0.x/commands/dev-show-tree.html
    servicemix/site/production/docs/5.0.x/commands/dev-system-property.html
    servicemix/site/production/docs/5.0.x/commands/dev-wait-for-service.html
    servicemix/site/production/docs/5.0.x/commands/dev-watch.html
    servicemix/site/production/docs/5.0.x/commands/feature-chooseurl.html
    servicemix/site/production/docs/5.0.x/commands/features-addUrl.html
    servicemix/site/production/docs/5.0.x/commands/features-info.html
    servicemix/site/production/docs/5.0.x/commands/features-install.html
    servicemix/site/production/docs/5.0.x/commands/features-list.html
    servicemix/site/production/docs/5.0.x/commands/features-listRepositories.html
    servicemix/site/production/docs/5.0.x/commands/features-listUrl.html
    servicemix/site/production/docs/5.0.x/commands/features-listVersions.html
    servicemix/site/production/docs/5.0.x/commands/features-refreshUrl.html
    servicemix/site/production/docs/5.0.x/commands/features-removeRepository.html
    servicemix/site/production/docs/5.0.x/commands/features-removeUrl.html
    servicemix/site/production/docs/5.0.x/commands/features-uninstall.html
    servicemix/site/production/docs/5.0.x/commands/index.html
    servicemix/site/production/docs/5.0.x/commands/instance-clone.html
    servicemix/site/production/docs/5.0.x/commands/jaas-cancel.html
    servicemix/site/production/docs/5.0.x/commands/jaas-manage.html
    servicemix/site/production/docs/5.0.x/commands/jaas-pending.html
    servicemix/site/production/docs/5.0.x/commands/jaas-realms.html
    servicemix/site/production/docs/5.0.x/commands/jaas-roleadd.html
    servicemix/site/production/docs/5.0.x/commands/jaas-roledel.html
    servicemix/site/production/docs/5.0.x/commands/jaas-update.html
    servicemix/site/production/docs/5.0.x/commands/jaas-useradd.html
    servicemix/site/production/docs/5.0.x/commands/jaas-userdel.html
    servicemix/site/production/docs/5.0.x/commands/jaas-users.html
    servicemix/site/production/docs/5.0.x/commands/log-clear.html
    servicemix/site/production/docs/5.0.x/commands/log-display-exception.html
    servicemix/site/production/docs/5.0.x/commands/log-display.html
    servicemix/site/production/docs/5.0.x/commands/log-get.html
    servicemix/site/production/docs/5.0.x/commands/log-set.html
    servicemix/site/production/docs/5.0.x/commands/log-tail.html
    servicemix/site/production/docs/5.0.x/commands/obr-addUrl.html
    servicemix/site/production/docs/5.0.x/commands/obr-deploy.html
    servicemix/site/production/docs/5.0.x/commands/obr-find.html
    servicemix/site/production/docs/5.0.x/commands/obr-info.html
    servicemix/site/production/docs/5.0.x/commands/obr-list.html
    servicemix/site/production/docs/5.0.x/commands/obr-listUrl.html
    servicemix/site/production/docs/5.0.x/commands/obr-refreshUrl.html
    servicemix/site/production/docs/5.0.x/commands/obr-removeUrl.html
    servicemix/site/production/docs/5.0.x/commands/obr-resolve.html
    servicemix/site/production/docs/5.0.x/commands/obr-source.html
    servicemix/site/production/docs/5.0.x/commands/obr-start.html
    servicemix/site/production/docs/5.0.x/commands/osgi-bundle-level.html
    servicemix/site/production/docs/5.0.x/commands/osgi-bundle-services.html
    servicemix/site/production/docs/5.0.x/commands/osgi-classes.html
    servicemix/site/production/docs/5.0.x/commands/osgi-find-class.html
    servicemix/site/production/docs/5.0.x/commands/osgi-headers.html
    servicemix/site/production/docs/5.0.x/commands/osgi-info.html
    servicemix/site/production/docs/5.0.x/commands/osgi-install.html
    servicemix/site/production/docs/5.0.x/commands/osgi-list.html
    servicemix/site/production/docs/5.0.x/commands/osgi-ls.html
    servicemix/site/production/docs/5.0.x/commands/osgi-name.html
    servicemix/site/production/docs/5.0.x/commands/osgi-refresh.html
    servicemix/site/production/docs/5.0.x/commands/osgi-resolve.html
    servicemix/site/production/docs/5.0.x/commands/osgi-restart.html
    servicemix/site/production/docs/5.0.x/commands/osgi-shutdown.html
    servicemix/site/production/docs/5.0.x/commands/osgi-start-level.html
    servicemix/site/production/docs/5.0.x/commands/osgi-start.html
    servicemix/site/production/docs/5.0.x/commands/osgi-stop.html
    servicemix/site/production/docs/5.0.x/commands/osgi-uninstall.html
    servicemix/site/production/docs/5.0.x/commands/osgi-update.html
    servicemix/site/production/docs/5.0.x/commands/osgi-version.html
    servicemix/site/production/docs/5.0.x/commands/packages-exports.html
    servicemix/site/production/docs/5.0.x/commands/packages-imports.html
    servicemix/site/production/docs/5.0.x/commands/shell-cat.html
    servicemix/site/production/docs/5.0.x/commands/shell-clear.html
    servicemix/site/production/docs/5.0.x/commands/shell-each.html
    servicemix/site/production/docs/5.0.x/commands/shell-echo.html
    servicemix/site/production/docs/5.0.x/commands/shell-exec.html
    servicemix/site/production/docs/5.0.x/commands/shell-grep.html
    servicemix/site/production/docs/5.0.x/commands/shell-head.html
    servicemix/site/production/docs/5.0.x/commands/shell-history.html
    servicemix/site/production/docs/5.0.x/commands/shell-if.html
    servicemix/site/production/docs/5.0.x/commands/shell-info.html
    servicemix/site/production/docs/5.0.x/commands/shell-java.html
    servicemix/site/production/docs/5.0.x/commands/shell-logout.html
    servicemix/site/production/docs/5.0.x/commands/shell-more.html
    servicemix/site/production/docs/5.0.x/commands/shell-new.html
    servicemix/site/production/docs/5.0.x/commands/shell-printf.html
    servicemix/site/production/docs/5.0.x/commands/shell-sleep.html
    servicemix/site/production/docs/5.0.x/commands/shell-sort.html
    servicemix/site/production/docs/5.0.x/commands/shell-source.html
    servicemix/site/production/docs/5.0.x/commands/shell-tac.html
    servicemix/site/production/docs/5.0.x/commands/shell-tail.html
    servicemix/site/production/docs/5.0.x/commands/shell-watch.html
    servicemix/site/production/docs/5.0.x/commands/ssh-ssh.html
    servicemix/site/production/docs/5.0.x/commands/ssh-sshd.html
    servicemix/site/production/docs/5.0.x/commands/toc.html
    servicemix/site/production/docs/5.0.x/commands/web-list.html
    servicemix/site/production/docs/5.0.x/commands/wrapper-install.html
    servicemix/site/production/docs/5.0.x/commercial.html
    servicemix/site/production/docs/5.0.x/contribute.html
    servicemix/site/production/docs/5.0.x/developers-guide/connect-console.html
    servicemix/site/production/docs/5.0.x/developers-guide/creating-bundles.html
    servicemix/site/production/docs/5.0.x/developers-guide/custom-distribution.html
    servicemix/site/production/docs/5.0.x/developers-guide/debugging.html
    servicemix/site/production/docs/5.0.x/developers-guide/developer-commands.html
    servicemix/site/production/docs/5.0.x/developers-guide/extending-console.html
    servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-add.html
    servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-create-kar.html
    servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-generate.html
    servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin-validate.html
    servicemix/site/production/docs/5.0.x/developers-guide/features-maven-plugin.html
    servicemix/site/production/docs/5.0.x/developers-guide/github-contributions.html
    servicemix/site/production/docs/5.0.x/developers-guide/index.html
    servicemix/site/production/docs/5.0.x/developers-guide/shell-syntax.html
    servicemix/site/production/docs/5.0.x/developers-guide/toc.html
    servicemix/site/production/docs/5.0.x/developers-guide/writing-tests.html
    servicemix/site/production/docs/5.0.x/index.html
    servicemix/site/production/docs/5.0.x/karaf/index.html
    servicemix/site/production/docs/5.0.x/karaf/toc.html
    servicemix/site/production/docs/5.0.x/quickstart/activemq.html
    servicemix/site/production/docs/5.0.x/quickstart/camel.html
    servicemix/site/production/docs/5.0.x/quickstart/console.html
    servicemix/site/production/docs/5.0.x/quickstart/features.html
    servicemix/site/production/docs/5.0.x/quickstart/index.html
    servicemix/site/production/docs/5.0.x/quickstart/installation.html
    servicemix/site/production/docs/5.0.x/quickstart/quickstart.pdf.html
    servicemix/site/production/docs/5.0.x/quickstart/toc.html
    servicemix/site/production/docs/5.0.x/user/index.html
    servicemix/site/production/docs/5.0.x/user/technology-selection.html
    servicemix/site/production/docs/5.0.x/user/toc.html
    servicemix/site/production/docs/5.0.x/user/what-is-smx4.html
    servicemix/site/production/docs/5.0.x/users-guide/child-instances.html
    servicemix/site/production/docs/5.0.x/users-guide/configuration.html
    servicemix/site/production/docs/5.0.x/users-guide/deployer.html
    servicemix/site/production/docs/5.0.x/users-guide/directory-structure.html
    servicemix/site/production/docs/5.0.x/users-guide/failover.html
    servicemix/site/production/docs/5.0.x/users-guide/http.html
    servicemix/site/production/docs/5.0.x/users-guide/index.html
    servicemix/site/production/docs/5.0.x/users-guide/installation.html
    servicemix/site/production/docs/5.0.x/users-guide/jmx.html
    servicemix/site/production/docs/5.0.x/users-guide/jre-tuning.html
    servicemix/site/production/docs/5.0.x/users-guide/kar.html
    servicemix/site/production/docs/5.0.x/users-guide/logging-system.html
    servicemix/site/production/docs/5.0.x/users-guide/provisioning.html
    servicemix/site/production/docs/5.0.x/users-guide/remote-console.html
    servicemix/site/production/docs/5.0.x/users-guide/security.html
    servicemix/site/production/docs/5.0.x/users-guide/start-stop.html
    servicemix/site/production/docs/5.0.x/users-guide/toc.html
    servicemix/site/production/docs/5.0.x/users-guide/using-console.html
    servicemix/site/production/docs/5.0.x/users-guide/web-applications.html
    servicemix/site/production/docs/5.0.x/users-guide/web-console.html
    servicemix/site/production/docs/5.0.x/users-guide/wrapper.html

Modified: servicemix/site/production/docs/5.0.x/activemq/activemq-camel-example.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/activemq/activemq-camel-example.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/activemq/activemq-camel-example.html (original)
+++ servicemix/site/production/docs/5.0.x/activemq/activemq-camel-example.html Wed May 28 08:20:15 2014
@@ -77,58 +77,12 @@
 </ul>
         </div>
         <div id="body">
-                              <h2 id="UsingActiveMQwithCamel">Using ActiveMQ with Camel</h2><h3 id="UsingSpringDM">Using Spring-DM</h3><p>It is often easy to define two application contexts for spring-dm, it helps you re-use configuration in Junit tests<br/>and cleanly separates OSGi from the normal spring application contexts.</p><p>You define these files in a bundle by adding them to the classpath under META-INF/spring</p><h4 id="OSGiApplicationcontext">OSGi Application context</h4><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
-  xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-  xmlns:tx=&quot;http://www.springframework.org/schema/tx&quot;
-  xmlns:ctx=&quot;http://www.springframework.org/schema/context&quot;
-  xmlns:osgi=&quot;http://www.springframework.org/schema/osgi&quot;
-  xmlns:osgix=&quot;http://www.springframework.org/schema/osgi-compendium&quot;
-  xsi:schemaLocation=&quot;
-    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd
-    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx.xsd
-    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd
-    http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context.xsd
-    http://www.springframework.org/schema/osgi http://www.springframework.org/schema/osgi/spring-osgi.xsd
-    http://www.springframework.org/schema/osgi-compendium http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd&quot;&gt;
-
-    &lt;!-- Make sure we use the ServiceMix provided connection pool in our beans --&gt;
-    &lt;osgi:reference id=&quot;jmsConnectionPool&quot; interface=&quot;javax.jms.ConnectionFactory&quot;/&gt;
-
-&lt;/beans&gt;</code></pre></div><h4 id="Normalspringapplicationcontext.">Normal spring application context.</h4><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;beans xmlns=&quot;http://www.springframework.org/schema/beans&quot;
-       xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot;
-       xmlns:camel=&quot;http://camel.apache.org/schema/spring&quot;
-       xsi:schemaLocation=&quot;
-        http://www.springframework.org/schema/beans
-        http://www.springframework.org/schema/beans/spring-beans-2.5.xsd
-        http://camel.apache.org/schema/spring
-        http://camel.apache.org/schema/spring/camel-spring-${camel-version}.xsd&quot;&gt;
-
-    &lt;camelContext xmlns=&quot;http://camel.apache.org/schema/spring&quot;&gt;
-        &lt;route&gt;
-            &lt;from uri=&quot;jms:queue:start&quot;/&gt;
-            &lt;to uri=&quot;mock:result&quot;/&gt;
-        &lt;/route&gt;
-    &lt;/camelContext&gt;
-
-    &lt;!-- This bean will import use the OSGi service from the context above --&gt;
-    &lt;bean id=&quot;jms&quot; class=&quot;org.apache.camel.component.jms.JmsComponent&quot;&gt;
-        &lt;property name=&quot;connectionFactory&quot; ref=&quot;jmsConnectionPool&quot; /&gt;
-        &lt;!-- If you have a transaction manager configured
-        &lt;property name=&quot;transacted&quot; value=&quot;true&quot; /&gt;
-        &lt;property name=&quot;transactionManager&quot; ref=&quot;transactionManager&quot; /&gt;
-        --&gt;
-    &lt;/bean&gt;
-
-&lt;/beans&gt;</code></pre></div>
+                              <h2 id="UsingActiveMQwithCamel">Using ActiveMQ with Camel</h2><h3 id="UsingSpringDM">Using Spring-DM</h3><p>It is often easy to define two application contexts for spring-dm, it helps you re-use configuration in Junit tests<br/>and cleanly separates OSGi from the normal spring application contexts.</p><p>You define these files in a bundle by adding them to the classpath under META-INF/spring</p><h4 id="OSGiApplicationcontext">OSGi Application context</h4><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:tx=</span><span class="s">&quot;http://www.springframework.org/schema
 /tx&quot;</span>&#x000A;  <span class="na">xmlns:ctx=</span><span class="s">&quot;http://www.springframework.org/schema/context&quot;</span>&#x000A;  <span class="na">xmlns:osgi=</span><span class="s">&quot;http://www.springframework.org/schema/osgi&quot;</span>&#x000A;  <span class="na">xmlns:osgix=</span><span class="s">&quot;http://www.springframework.org/schema/osgi-compendium&quot;</span>&#x000A;  <span class="na">xsi:schemaLocation=</span><span class="s">&quot;</span>&#x000A;<span class="s">    http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans.xsd</span>&#x000A;<span class="s">    http://www.springframework.org/schema/tx http://www.springframework.org/schema/tx/spring-tx.xsd</span>&#x000A;<span class="s">    http://www.springframework.org/schema/aop http://www.springframework.org/schema/aop/spring-aop.xsd</span>&#x000A;<span class="s">    http://www.springframework.org/schema/context http://www.springframework.org/schema/conte
 xt/spring-context.xsd</span>&#x000A;<span class="s">    http://www.springframework.org/schema/osgi http://www.springframework.org/schema/osgi/spring-osgi.xsd</span>&#x000A;<span class="s">    http://www.springframework.org/schema/osgi-compendium http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="c">&lt;!-- Make sure we use the ServiceMix provided connection pool in our beans --&gt;</span>&#x000A;    <span class="nt">&lt;osgi:reference</span> <span class="na">id=</span><span class="s">&quot;jmsConnectionPool&quot;</span> <span class="na">interface=</span><span class="s">&quot;javax.jms.ConnectionFactory&quot;</span><span class="nt">/&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/beans&gt;</span>&#x000A;</pre></div>&#x000A;</div><h4 id="Normalspringapplicationcontext.">Normal spring application context.</h4><div class="syntax"><div class="highlight"><pre><span class="cp">&lt;?xml v
 ersion=&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-${camel-version}.xsd&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="nt">&lt;camel
 Context</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;jms:queue:start&quot;</span><span class="nt">/&gt;</span>&#x000A;            <span class="nt">&lt;to</span> <span class="na">uri=</span><span class="s">&quot;mock:result&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="c">&lt;!-- This bean will import use the OSGi service from the context above --&gt;</span>&#x000A;    <span class="nt">&lt;bean</span> <span class="na">id=</span><span class="s">&quot;jms&quot;</span> <span class="na">class=</span><span class="s">&quot;org.apache.camel.component.jms.JmsComponent&quot;</span><span class="nt">&gt;</span>&#x0
 00A;        <span class="nt">&lt;property</span> <span class="na">name=</span><span class="s">&quot;connectionFactory&quot;</span> <span class="na">ref=</span><span class="s">&quot;jmsConnectionPool&quot;</span> <span class="nt">/&gt;</span>&#x000A;        <span class="c">&lt;!-- If you have a transaction manager configured</span>&#x000A;<span class="c">        &lt;property name=&quot;transacted&quot; value=&quot;true&quot; /&gt;</span>&#x000A;<span class="c">        &lt;property name=&quot;transactionManager&quot; ref=&quot;transactionManager&quot; /&gt;</span>&#x000A;<span class="c">        --&gt;</span>&#x000A;    <span class="nt">&lt;/bean&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/beans&gt;</span>&#x000A;</pre></div>&#x000A;</div>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/activemq/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/activemq/index.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/activemq/index.html (original)
+++ servicemix/site/production/docs/5.0.x/activemq/index.html Wed May 28 08:20:15 2014
@@ -82,7 +82,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/activemq/toc.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/activemq/toc.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/activemq/toc.html (original)
+++ servicemix/site/production/docs/5.0.x/activemq/toc.html Wed May 28 08:20:15 2014
@@ -89,7 +89,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/activiti/activiti-camel-example.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/activiti/activiti-camel-example.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/activiti/activiti-camel-example.html (original)
+++ servicemix/site/production/docs/5.0.x/activiti/activiti-camel-example.html Wed May 28 08:20:15 2014
@@ -82,160 +82,12 @@
                       <p>Due to issue <a href="https://issues.apache.org/jira/browse/SM-2287"</a>SM-2287</a>, Activiti needs to be added in ServiceMix 5 to the boot features before usage.</p>
                       <p>To add a boot feature, append the feature name to the <code>featuresBoot</code> list in the <code>etc/org.apache.karaf.features.cfg</code>. Afterwards, remove the data directory and start ServiceMix again.</p>
                     </div>
-                              <h2 id="UsingActivitiwithCamel">Using Activiti with Camel</h2><p>In this example we show an example howto Activiti can be used with Camel in Servicemix through Blueprint Container <br/><a href="http://aries.apache.org/modules/blueprint.html">http://aries.apache.org/modules/blueprint.html</a> </p><p>Before being able to run Activiti with Camel, you have to install some additional<br/>features into the container first to add support for the Activiti.</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-karaf@root&gt;  features:install activiti</code></pre></div><p>By default in Servicemix Activiti Engine use an Embedded (Local) H2 Database  the can be found under </p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-${karaf.data}/activiti/database.</code></pre></div><p>The Activiti engine is entry point for starting new process instances, deploy new process, querying for<br/>user tasks ecc.ecc and these information are stored in H2 DataBase</p><h3 id="Blueprintconfiguration">Blueprint configuration</h3><p>Let's see how you can set up the Camel context in a Blueprint configuration, as you can see<br/>Camel integration runs embedded with the Activiti Engine in the same Blueprint configuration. </p><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-
-&lt;?xml version=&quot;1.0&quot; encoding=&quot;UTF-8&quot;?&gt;
-&lt;blueprint xmlns=&quot;http://www.osgi.org/xmlns/blueprint/v1.0.0&quot;
-           xmlns:camel=&quot;http://camel.apache.org/schema/blueprint&quot;&gt;
-
-    &lt;!--
-        This Camel context contains the routes that interact with our BPMN process
-	
-	Here we instruct the Camel context to scan the classpath in
-	org.apache.servicemix.examples.activiti	
-	
-    --&gt;
-    &lt;camelContext id=&quot;camelContext&quot; xmlns=&quot;http://camel.apache.org/schema/blueprint&quot;&gt;
-        &lt;packageScan&gt;
-            &lt;package&gt;org.apache.servicemix.examples.activiti&lt;/package&gt;
-        &lt;/packageScan&gt;
-    &lt;/camelContext&gt;
-
-    &lt;!--
-        Obtain a reference to Activiti's RuntimeService - this reference will automatically
-        be picked up by the subsequent Activiti Camel component definition
-    --&gt;
-    &lt;reference id=&quot;runtimeService&quot; interface=&quot;org.activiti.engine.RuntimeService&quot; /&gt;
-
-    &lt;!--
-        Register a context provider to link the Camel context to the OrderProcess definition.
-        Doing this will allow your BPMN process to communicate with the Camel routes using the
-        ${camel} expression
-	The definition of SimpleContextProvider allows to connects a deployed process definition on the Activiti Engine to a Camel context.
-	Is possible to define a list of SimpleContextProviders for each process definition that you want to connect to a Camel contex
-
-    --&gt;
-    &lt;service interface=&quot;org.activiti.camel.ContextProvider&quot;&gt;
-        &lt;bean class=&quot;org.activiti.camel.SimpleContextProvider&quot;&gt;
-            &lt;argument value=&quot;OrderProcess&quot;/&gt;
-            &lt;argument ref=&quot;camelContext&quot;/&gt;
-        &lt;/bean&gt;
-    &lt;/service&gt;
-
-&lt;/blueprint&gt;
-</code></pre></div><h3 id="RouteDefinition">Route Definition</h3><div class="syntax"><pre name='code' class='brush: java; gutter: false;'><code>
-
-/**
- * Camel routes that interact with the business process defined in the
- * OSGI-INF/activiti/OrderProcess.bpmn20.xml file
- */
-public class ActivitiRouteBuilder extends RouteBuilder {
-
-    private final Helper helper = new Helper();
-
-    @Override
-    public void configure() throws Exception {
-        /*
-         * This route will start a new OrderProcess instance.  Using the PROCESS_KEY_PROPERTY, we are assigning a
-         * business key to our process to allow for easier correlation in later processing steps.  We are also
-         * sending a Map containing additional variables to add to the process instance.
-         */
-        from(&quot;file:var/activiti-camel/order&quot;)
-            .setBody(bean(helper))
-            .setProperty(PROCESS_KEY_PROPERTY, simple(&quot;file:name&quot;))
-            .to(&quot;activiti:OrderProcess&quot;)
-            .log(&quot;Process to handle incoming order file has been started (process instance id ${body})&quot;);
-
-        /*
-         * This route will notify a running OrderProcess of an order delivery event.  Here too, we are setting the
-         * PROCESS_KEY_PROPERTY to correlate the delivery message with right order process instance.
-         */
-        from(&quot;file:var/activiti-camel/delivery&quot;)
-            .log(&quot;Notifying process about delivery for order ${file:name}&quot;)
-            .setProperty(PROCESS_KEY_PROPERTY, simple(&quot;file:name&quot;))
-            .to(&quot;activiti:OrderProcess:receiveDelivery&quot;);
-
-        /*
-         * The BPMN process can also trigger Camel routes as part of the process.  In these routes, the variables that
-         * you added to the process are available as Exchange properties.  The next two routes will be triggered while
-         * processing the order and the order delivery.
-         */
-        from(&quot;activiti:OrderProcess:processOrder&quot;)
-            .log(&quot;Processing order ${property.orderid} created on ${property:timestamp}&quot;)
-            .log(&quot;  original message: ${property.message}&quot;);
-
-        from(&quot;activiti:OrderProcess:processDelivery&quot;)
-            .log(&quot;Processing delivery for order ${property.orderid} created on ${property:timestamp}&quot;)
-            .log(&quot;  original message: ${property.message}&quot;);
-    }
-
-    /*
-     * A few helper methods used for routing
-     */
-    public static final class Helper {
-
-        /*
-         * This method will extract information from the Exchange (using Camel annotations) and put them in a
-         * Map that will be used for setting up the process' variables.
-         */
-        @Handler
-        public Map getProcessVariables(@Body String body,
-                                       @Header(Exchange.FILE_NAME) String filename,
-                                       @Simple(&quot;${date:now:yyyy-MM-dd kk:mm:ss}&quot;) String timestamp) {
-            Map&lt;String, Object&gt; variables = new HashMap&lt;String, Object&gt;();
-            variables.put(&quot;message&quot;, body);
-            variables.put(&quot;orderid&quot;, filename);
-            variables.put(&quot;timestamp&quot;, timestamp);
-            return variables;
-        }
-    }
-}
-</code></pre></div><h3 id="Processdefinition">Process definition</h3><div class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-
-&lt;definitions xmlns=&quot;http://www.omg.org/spec/BPMN/20100524/MODEL&quot;
-	xmlns:xsi=&quot;http://www.w3.org/2001/XMLSchema-instance&quot; xmlns:activiti=&quot;http://activiti.org/bpmn&quot;
-	xmlns:bpmndi=&quot;http://www.omg.org/spec/BPMN/20100524/DI&quot; xmlns:omgdc=&quot;http://www.omg.org/spec/DD/20100524/DC&quot;
-	xmlns:omgdi=&quot;http://www.omg.org/spec/DD/20100524/DI&quot; typeLanguage=&quot;http://www.w3.org/2001/XMLSchema&quot;
-	expressionLanguage=&quot;http://www.w3.org/1999/XPath&quot; targetNamespace=&quot;http://www.activiti.org/test&quot;&gt;
-
-
-	&lt;process id=&quot;OrderProcess&quot; isExecutable=&quot;true&quot;&gt;
-
-		&lt;startEvent id=&quot;start&quot; /&gt;
-
-		&lt;sequenceFlow id=&quot;flow1&quot; sourceRef=&quot;start&quot; targetRef=&quot;processOrder&quot; /&gt;
-
-		&lt;serviceTask id=&quot;processOrder&quot;
-			activiti:delegateExpression=&quot;${camel}&quot; /&gt;
-
-		&lt;sequenceFlow id=&quot;flow2&quot; sourceRef=&quot;processOrder&quot;
-			targetRef=&quot;receiveDelivery&quot; /&gt;
-
-		&lt;receiveTask id=&quot;receiveDelivery&quot; name=&quot;Wait for Delivery&quot; /&gt;
-
-		&lt;sequenceFlow id=&quot;flow3&quot; sourceRef=&quot;receiveDelivery&quot;
-			targetRef=&quot;processDelivery&quot; /&gt;
-
-		&lt;serviceTask id=&quot;processDelivery&quot;
-			activiti:delegateExpression=&quot;${camel}&quot; /&gt;
-
-		&lt;sequenceFlow id=&quot;flow4&quot; sourceRef=&quot;processDelivery&quot;
-			targetRef=&quot;end&quot; /&gt;
-
-		&lt;endEvent id=&quot;end&quot; /&gt;
-
-	&lt;/process&gt;
-
-&lt;/definitions&gt;
-</code></pre></div><p>The process presented here above define a simple order process, that process the incoming orders and subsequently waits for its delivery.  Once the delivery notification has been received, <br/>another bit of processing occurs before the business process ends.</p><p>This process defines the BPMN definition and is automatically deployed as soon as bundle is started:</p><div class="syntax"><pre name='code' class='brush: text; gutter: false;'><code>
-start --&gt; processOrder --&gt; waitForDelivery --&gt; processDelivery --&gt; end</code></pre></div><p>When the service task is executed by the Activiti Engine the execution is delegated to the CamelBehaviour class, which will send a message containing<br/>all process variables to an Activiti endpoint defined in the Camel context.<br/>This behavior is obtained through the use the delegateExpression in the Java service task</p>
+                              <h2 id="UsingActivitiwithCamel">Using Activiti with Camel</h2><p>In this example we show an example howto Activiti can be used with Camel in Servicemix through Blueprint Container <br/><a href="http://aries.apache.org/modules/blueprint.html">http://aries.apache.org/modules/blueprint.html</a> </p><p>Before being able to run Activiti with Camel, you have to install some additional<br/>features into the container first to add support for the Activiti.</p><div class="syntax"><div class="highlight"><pre>karaf@root&gt;  features:install activiti&#x000A;</pre></div>&#x000A;</div><p>By default in Servicemix Activiti Engine use an Embedded (Local) H2 Database  the can be found under </p><div class="syntax"><div class="highlight"><pre>${karaf.data}/activiti/database.&#x000A;</pre></div>&#x000A;</div><p>The Activiti engine is entry point for starting new process instances, deploy new process, querying for<br/>user tasks ecc.ecc and these information are stored in 
 H2 DataBase</p><h3 id="Blueprintconfiguration">Blueprint configuration</h3><p>Let's see how you can set up the Camel context in a Blueprint configuration, as you can see<br/>Camel integration runs embedded with the Activiti Engine in the same Blueprint configuration. </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> <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:camel=</span><span class="s">&quot;http://camel.apache.org/schema/blueprint&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;    <span class="c">&lt;!--</span>&#x000A;<span class="c">        This Camel context contains the routes that interact with our BPMN process</span>&#x000A;<span class="c">	</span>&#x000A;<span class="c">	Here we instruct the Camel context to scan the classpath i
 n</span>&#x000A;<span class="c">	org.apache.servicemix.examples.activiti	</span>&#x000A;<span class="c">	</span>&#x000A;<span class="c">    --&gt;</span>&#x000A;    <span class="nt">&lt;camelContext</span> <span class="na">id=</span><span class="s">&quot;camelContext&quot;</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;packageScan&gt;</span>&#x000A;            <span class="nt">&lt;package&gt;</span>org.apache.servicemix.examples.activiti<span class="nt">&lt;/package&gt;</span>&#x000A;        <span class="nt">&lt;/packageScan&gt;</span>&#x000A;    <span class="nt">&lt;/camelContext&gt;</span>&#x000A;&#x000A;    <span class="c">&lt;!--</span>&#x000A;<span class="c">        Obtain a reference to Activiti&#39;s RuntimeService - this reference will automatically</span>&#x000A;<span class="c">        be picked up by the subsequent Activiti Camel component defin
 ition</span>&#x000A;<span class="c">    --&gt;</span>&#x000A;    <span class="nt">&lt;reference</span> <span class="na">id=</span><span class="s">&quot;runtimeService&quot;</span> <span class="na">interface=</span><span class="s">&quot;org.activiti.engine.RuntimeService&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;    <span class="c">&lt;!--</span>&#x000A;<span class="c">        Register a context provider to link the Camel context to the OrderProcess definition.</span>&#x000A;<span class="c">        Doing this will allow your BPMN process to communicate with the Camel routes using the</span>&#x000A;<span class="c">        ${camel} expression</span>&#x000A;<span class="c">	The definition of SimpleContextProvider allows to connects a deployed process definition on the Activiti Engine to a Camel context.</span>&#x000A;<span class="c">	Is possible to define a list of SimpleContextProviders for each process definition that you want to connect to a Camel contex</span>&#x000A
 ;&#x000A;<span class="c">    --&gt;</span>&#x000A;    <span class="nt">&lt;service</span> <span class="na">interface=</span><span class="s">&quot;org.activiti.camel.ContextProvider&quot;</span><span class="nt">&gt;</span>&#x000A;        <span class="nt">&lt;bean</span> <span class="na">class=</span><span class="s">&quot;org.activiti.camel.SimpleContextProvider&quot;</span><span class="nt">&gt;</span>&#x000A;            <span class="nt">&lt;argument</span> <span class="na">value=</span><span class="s">&quot;OrderProcess&quot;</span><span class="nt">/&gt;</span>&#x000A;            <span class="nt">&lt;argument</span> <span class="na">ref=</span><span class="s">&quot;camelContext&quot;</span><span class="nt">/&gt;</span>&#x000A;        <span class="nt">&lt;/bean&gt;</span>&#x000A;    <span class="nt">&lt;/service&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/blueprint&gt;</span>&#x000A;</pre></div>&#x000A;</div><h3 id="RouteDefinition">Route Definition</h3><div class="syntax"><div cl
 ass="highlight"><pre><span class="cm">/**</span>&#x000A;<span class="cm"> * Camel routes that interact with the business process defined in the</span>&#x000A;<span class="cm"> * OSGI-INF/activiti/OrderProcess.bpmn20.xml file</span>&#x000A;<span class="cm"> */</span>&#x000A;<span class="kd">public</span> <span class="kd">class</span> <span class="nc">ActivitiRouteBuilder</span> <span class="kd">extends</span> <span class="n">RouteBuilder</span> <span class="o">{</span>&#x000A;&#x000A;    <span class="kd">private</span> <span class="kd">final</span> <span class="n">Helper</span> <span class="n">helper</span> <span class="o">=</span> <span class="k">new</span> <span class="n">Helper</span><span class="o">();</span>&#x000A;&#x000A;    <span class="nd">@Override</span>&#x000A;    <span class="kd">public</span> <span class="kt">void</span> <span class="nf">configure</span><span class="o">()</span> <span class="kd">throws</span> <span class="n">Exception</span> <span class="o">{</span>&#x0
 00A;        <span class="cm">/*</span>&#x000A;<span class="cm">         * This route will start a new OrderProcess instance.  Using the PROCESS_KEY_PROPERTY, we are assigning a</span>&#x000A;<span class="cm">         * business key to our process to allow for easier correlation in later processing steps.  We are also</span>&#x000A;<span class="cm">         * sending a Map containing additional variables to add to the process instance.</span>&#x000A;<span class="cm">         */</span>&#x000A;        <span class="n">from</span><span class="o">(</span><span class="s">&quot;file:var/activiti-camel/order&quot;</span><span class="o">)</span>&#x000A;            <span class="o">.</span><span class="na">setBody</span><span class="o">(</span><span class="n">bean</span><span class="o">(</span><span class="n">helper</span><span class="o">))</span>&#x000A;            <span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="n">PROCESS_KEY_PROPERTY</span><spa
 n class="o">,</span> <span class="n">simple</span><span class="o">(</span><span class="s">&quot;file:name&quot;</span><span class="o">))</span>&#x000A;            <span class="o">.</span><span class="na">to</span><span class="o">(</span><span class="s">&quot;activiti:OrderProcess&quot;</span><span class="o">)</span>&#x000A;            <span class="o">.</span><span class="na">log</span><span class="o">(</span><span class="s">&quot;Process to handle incoming order file has been started (process instance id ${body})&quot;</span><span class="o">);</span>&#x000A;&#x000A;        <span class="cm">/*</span>&#x000A;<span class="cm">         * This route will notify a running OrderProcess of an order delivery event.  Here too, we are setting the</span>&#x000A;<span class="cm">         * PROCESS_KEY_PROPERTY to correlate the delivery message with right order process instance.</span>&#x000A;<span class="cm">         */</span>&#x000A;        <span class="n">from</span><span class="o">(</span><sp
 an class="s">&quot;file:var/activiti-camel/delivery&quot;</span><span class="o">)</span>&#x000A;            <span class="o">.</span><span class="na">log</span><span class="o">(</span><span class="s">&quot;Notifying process about delivery for order ${file:name}&quot;</span><span class="o">)</span>&#x000A;            <span class="o">.</span><span class="na">setProperty</span><span class="o">(</span><span class="n">PROCESS_KEY_PROPERTY</span><span class="o">,</span> <span class="n">simple</span><span class="o">(</span><span class="s">&quot;file:name&quot;</span><span class="o">))</span>&#x000A;            <span class="o">.</span><span class="na">to</span><span class="o">(</span><span class="s">&quot;activiti:OrderProcess:receiveDelivery&quot;</span><span class="o">);</span>&#x000A;&#x000A;        <span class="cm">/*</span>&#x000A;<span class="cm">         * The BPMN process can also trigger Camel routes as part of the process.  In these routes, the variables that</span>&#x000A;<span cl
 ass="cm">         * you added to the process are available as Exchange properties.  The next two routes will be triggered while</span>&#x000A;<span class="cm">         * processing the order and the order delivery.</span>&#x000A;<span class="cm">         */</span>&#x000A;        <span class="n">from</span><span class="o">(</span><span class="s">&quot;activiti:OrderProcess:processOrder&quot;</span><span class="o">)</span>&#x000A;            <span class="o">.</span><span class="na">log</span><span class="o">(</span><span class="s">&quot;Processing order ${property.orderid} created on ${property:timestamp}&quot;</span><span class="o">)</span>&#x000A;            <span class="o">.</span><span class="na">log</span><span class="o">(</span><span class="s">&quot;  original message: ${property.message}&quot;</span><span class="o">);</span>&#x000A;&#x000A;        <span class="n">from</span><span class="o">(</span><span class="s">&quot;activiti:OrderProcess:processDelivery&quot;</span><span cla
 ss="o">)</span>&#x000A;            <span class="o">.</span><span class="na">log</span><span class="o">(</span><span class="s">&quot;Processing delivery for order ${property.orderid} created on ${property:timestamp}&quot;</span><span class="o">)</span>&#x000A;            <span class="o">.</span><span class="na">log</span><span class="o">(</span><span class="s">&quot;  original message: ${property.message}&quot;</span><span class="o">);</span>&#x000A;    <span class="o">}</span>&#x000A;&#x000A;    <span class="cm">/*</span>&#x000A;<span class="cm">     * A few helper methods used for routing</span>&#x000A;<span class="cm">     */</span>&#x000A;    <span class="kd">public</span> <span class="kd">static</span> <span class="kd">final</span> <span class="kd">class</span> <span class="nc">Helper</span> <span class="o">{</span>&#x000A;&#x000A;        <span class="cm">/*</span>&#x000A;<span class="cm">         * This method will extract information from the Exchange (using Camel annotations)
  and put them in a</span>&#x000A;<span class="cm">         * Map that will be used for setting up the process&#39; variables.</span>&#x000A;<span class="cm">         */</span>&#x000A;        <span class="nd">@Handler</span>&#x000A;        <span class="kd">public</span> <span class="n">Map</span> <span class="nf">getProcessVariables</span><span class="o">(</span><span class="nd">@Body</span> <span class="n">String</span> <span class="n">body</span><span class="o">,</span>&#x000A;                                       <span class="nd">@Header</span><span class="o">(</span><span class="n">Exchange</span><span class="o">.</span><span class="na">FILE_NAME</span><span class="o">)</span> <span class="n">String</span> <span class="n">filename</span><span class="o">,</span>&#x000A;                                       <span class="nd">@Simple</span><span class="o">(</span><span class="s">&quot;${date:now:yyyy-MM-dd kk:mm:ss}&quot;</span><span class="o">)</span> <span class="n">String</span>
  <span class="n">timestamp</span><span class="o">)</span> <span class="o">{</span>&#x000A;            <span class="n">Map</span><span class="o">&lt;</span><span class="n">String</span><span class="o">,</span> <span class="n">Object</span><span class="o">&gt;</span> <span class="n">variables</span> <span class="o">=</span> <span class="k">new</span> <span class="n">HashMap</span><span class="o">&lt;</span><span class="n">String</span><span class="o">,</span> <span class="n">Object</span><span class="o">&gt;();</span>&#x000A;            <span class="n">variables</span><span class="o">.</span><span class="na">put</span><span class="o">(</span><span class="s">&quot;message&quot;</span><span class="o">,</span> <span class="n">body</span><span class="o">);</span>&#x000A;            <span class="n">variables</span><span class="o">.</span><span class="na">put</span><span class="o">(</span><span class="s">&quot;orderid&quot;</span><span class="o">,</span> <span class="n">filename</span><span
  class="o">);</span>&#x000A;            <span class="n">variables</span><span class="o">.</span><span class="na">put</span><span class="o">(</span><span class="s">&quot;timestamp&quot;</span><span class="o">,</span> <span class="n">timestamp</span><span class="o">);</span>&#x000A;            <span class="k">return</span> <span class="n">variables</span><span class="o">;</span>&#x000A;        <span class="o">}</span>&#x000A;    <span class="o">}</span>&#x000A;<span class="o">}</span>&#x000A;</pre></div>&#x000A;</div><h3 id="Processdefinition">Process definition</h3><div class="syntax"><div class="highlight"><pre><span class="nt">&lt;definitions</span> <span class="na">xmlns=</span><span class="s">&quot;http://www.omg.org/spec/BPMN/20100524/MODEL&quot;</span>&#x000A;	<span class="na">xmlns:xsi=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema-instance&quot;</span> <span class="na">xmlns:activiti=</span><span class="s">&quot;http://activiti.org/bpmn&quot;</span>&#x000A;	<sp
 an class="na">xmlns:bpmndi=</span><span class="s">&quot;http://www.omg.org/spec/BPMN/20100524/DI&quot;</span> <span class="na">xmlns:omgdc=</span><span class="s">&quot;http://www.omg.org/spec/DD/20100524/DC&quot;</span>&#x000A;	<span class="na">xmlns:omgdi=</span><span class="s">&quot;http://www.omg.org/spec/DD/20100524/DI&quot;</span> <span class="na">typeLanguage=</span><span class="s">&quot;http://www.w3.org/2001/XMLSchema&quot;</span>&#x000A;	<span class="na">expressionLanguage=</span><span class="s">&quot;http://www.w3.org/1999/XPath&quot;</span> <span class="na">targetNamespace=</span><span class="s">&quot;http://www.activiti.org/test&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;&#x000A;	<span class="nt">&lt;process</span> <span class="na">id=</span><span class="s">&quot;OrderProcess&quot;</span> <span class="na">isExecutable=</span><span class="s">&quot;true&quot;</span><span class="nt">&gt;</span>&#x000A;&#x000A;		<span class="nt">&lt;startEvent</span> <span class
 ="na">id=</span><span class="s">&quot;start&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;		<span class="nt">&lt;sequenceFlow</span> <span class="na">id=</span><span class="s">&quot;flow1&quot;</span> <span class="na">sourceRef=</span><span class="s">&quot;start&quot;</span> <span class="na">targetRef=</span><span class="s">&quot;processOrder&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;		<span class="nt">&lt;serviceTask</span> <span class="na">id=</span><span class="s">&quot;processOrder&quot;</span>&#x000A;			<span class="na">activiti:delegateExpression=</span><span class="s">&quot;${camel}&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;		<span class="nt">&lt;sequenceFlow</span> <span class="na">id=</span><span class="s">&quot;flow2&quot;</span> <span class="na">sourceRef=</span><span class="s">&quot;processOrder&quot;</span>&#x000A;			<span class="na">targetRef=</span><span class="s">&quot;receiveDelivery&quot;</span> <span class="nt">/&gt;</sp
 an>&#x000A;&#x000A;		<span class="nt">&lt;receiveTask</span> <span class="na">id=</span><span class="s">&quot;receiveDelivery&quot;</span> <span class="na">name=</span><span class="s">&quot;Wait for Delivery&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;		<span class="nt">&lt;sequenceFlow</span> <span class="na">id=</span><span class="s">&quot;flow3&quot;</span> <span class="na">sourceRef=</span><span class="s">&quot;receiveDelivery&quot;</span>&#x000A;			<span class="na">targetRef=</span><span class="s">&quot;processDelivery&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;		<span class="nt">&lt;serviceTask</span> <span class="na">id=</span><span class="s">&quot;processDelivery&quot;</span>&#x000A;			<span class="na">activiti:delegateExpression=</span><span class="s">&quot;${camel}&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;		<span class="nt">&lt;sequenceFlow</span> <span class="na">id=</span><span class="s">&quot;flow4&quot;</span> <span class="
 na">sourceRef=</span><span class="s">&quot;processDelivery&quot;</span>&#x000A;			<span class="na">targetRef=</span><span class="s">&quot;end&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;		<span class="nt">&lt;endEvent</span> <span class="na">id=</span><span class="s">&quot;end&quot;</span> <span class="nt">/&gt;</span>&#x000A;&#x000A;	<span class="nt">&lt;/process&gt;</span>&#x000A;&#x000A;<span class="nt">&lt;/definitions&gt;</span>&#x000A;</pre></div>&#x000A;</div><p>The process presented here above define a simple order process, that process the incoming orders and subsequently waits for its delivery.  Once the delivery notification has been received, <br/>another bit of processing occurs before the business process ends.</p><p>This process defines the BPMN definition and is automatically deployed as soon as bundle is started:</p><div class="syntax"><div class="highlight"><pre>start --&gt; processOrder --&gt; waitForDelivery --&gt; processDelivery --&gt; end&#x000A;
 </pre></div>&#x000A;</div><p>When the service task is executed by the Activiti Engine the execution is delegated to the CamelBehaviour class, which will send a message containing<br/>all process variables to an Activiti endpoint defined in the Camel context.<br/>This behavior is obtained through the use the delegateExpression in the Java service task</p>
         </div>
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/activiti/index.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/activiti/index.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/activiti/index.html (original)
+++ servicemix/site/production/docs/5.0.x/activiti/index.html Wed May 28 08:20:15 2014
@@ -87,7 +87,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>

Modified: servicemix/site/production/docs/5.0.x/activiti/toc.html
URL: http://svn.apache.org/viewvc/servicemix/site/production/docs/5.0.x/activiti/toc.html?rev=1597941&r1=1597940&r2=1597941&view=diff
==============================================================================
--- servicemix/site/production/docs/5.0.x/activiti/toc.html (original)
+++ servicemix/site/production/docs/5.0.x/activiti/toc.html Wed May 28 08:20:15 2014
@@ -95,7 +95,7 @@
       
           </div>
     <div id="siteFooter">
-      &copy; 2008-2012 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
+      &copy; 2008-2014 The Apache Software Foundation - <a href="http://servicemix.apache.org/site/privacy-policy.html">Privacy Policy</a>
       <br/>
       Apache ServiceMix, ServiceMix, Apache, the Apache feather logo, and the Apache ServiceMix project logo are trademarks of The Apache Software Foundation.
     </div>



Mime
View raw message