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>
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:tx="http://www.springframework.org/schema/tx"
- xmlns:ctx="http://www.springframework.org/schema/context"
- xmlns:osgi="http://www.springframework.org/schema/osgi"
- xmlns:osgix="http://www.springframework.org/schema/osgi-compendium"
- xsi:schemaLocation="
- 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">
-
- <!-- Make sure we use the ServiceMix provided connection pool in our
beans -->
- <osgi:reference id="jmsConnectionPool"
interface="javax.jms.ConnectionFactory"/>
-
-</beans></code></pre></div><h4
id="Normalspringapplicationcontext.">Normal spring application
context.</h4><div class="syntax"><pre name='code' class='brush: xml; gutter:
false;'><code>
-<?xml version="1.0" encoding="UTF-8"?>
-<beans xmlns="http://www.springframework.org/schema/beans"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
- xmlns:camel="http://camel.apache.org/schema/spring"
- xsi:schemaLocation="
- 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">
-
- <camelContext
xmlns="http://camel.apache.org/schema/spring">
- <route>
- <from uri="jms:queue:start"/>
- <to uri="mock:result"/>
- </route>
- </camelContext>
-
- <!-- This bean will import use the OSGi service from the context above
-->
- <bean id="jms"
class="org.apache.camel.component.jms.JmsComponent">
- <property name="connectionFactory"
ref="jmsConnectionPool" />
- <!-- If you have a transaction manager configured
- <property name="transacted" value="true" />
- <property name="transactionManager"
ref="transactionManager" />
- -->
- </bean>
-
-</beans></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"><?xml
version="1.0" encoding="UTF-8"?></span>
<span
class="nt"><beans</span> <span class="na">xmlns=</span><span
class="s">"http://www.springframework.org/schema/beans"</span>

<span class="na">xmlns:xsi=</span><span
class="s">"http://www.w3.org/2001/XMLSchema-instance"</span>

<span class="na">xmlns:tx=</span><span
class="s">"http://www.springframework.org/schema
/tx"</span>
 <span class="na">xmlns:ctx=</span><span
class="s">"http://www.springframework.org/schema/context"</span>

<span class="na">xmlns:osgi=</span><span
class="s">"http://www.springframework.org/schema/osgi"</span>

<span class="na">xmlns:osgix=</span><span
class="s">"http://www.springframework.org/schema/osgi-compendium"</span>

<span class="na">xsi:schemaLocation=</span><span
class="s">"</span>
<span class="s">
http://www.springframework.org/schema/beans
http://www.springframework.org/schema/beans/spring-beans.xsd</span>
<span
class="s"> http://www.springframework.org/schema/tx
http://www.springframework.org/schema/tx/spring-tx.xsd</span>
<span
class="s"> http://www.springframework.org/schema/aop
http://www.springframework.org/schema/aop/spring-aop.xsd</span>
<span
class="s"> http://www.springframework.org/schema/context
http://www.springframework.org/schema/conte
xt/spring-context.xsd</span>
<span class="s">
http://www.springframework.org/schema/osgi
http://www.springframework.org/schema/osgi/spring-osgi.xsd</span>
<span
class="s"> http://www.springframework.org/schema/osgi-compendium
http://www.springframework.org/schema/osgi-compendium/spring-osgi-compendium.xsd"</span><span
class="nt">></span>

 <span class="c"><!-- Make sure we
use the ServiceMix provided connection pool in our beans --></span>

<span class="nt"><osgi:reference</span> <span class="na">id=</span><span
class="s">"jmsConnectionPool"</span> <span
class="na">interface=</span><span
class="s">"javax.jms.ConnectionFactory"</span><span
class="nt">/></span>

<span
class="nt"></beans></span>
</pre></div>
</div><h4
id="Normalspringapplicationcontext.">Normal spring application
context.</h4><div class="syntax"><div class="highlight"><pre><span
class="cp"><?xml v
ersion="1.0" encoding="UTF-8"?></span>
<span
class="nt"><beans</span> <span class="na">xmlns=</span><span
class="s">"http://www.springframework.org/schema/beans"</span>

<span class="na">xmlns:xsi=</span><span
class="s">"http://www.w3.org/2001/XMLSchema-instance"</span>

<span class="na">xmlns:camel=</span><span
class="s">"http://camel.apache.org/schema/spring"</span>

<span class="na">xsi:schemaLocation=</span><span
class="s">"</span>
<span class="s">
http://www.springframework.org/schema/beans</span>
<span class="s">
http://www.springframework.org/schema/beans/spring-beans-2.5.xsd</span>
<span
class="s"> http://camel.apache.org/schema/spring</span>
<span
class="s">
http://camel.apache.org/schema/spring/camel-spring-${camel-version}.xsd"</span><span
class="nt">></span>

 <span class="nt"><camel
Context</span> <span class="na">xmlns=</span><span
class="s">"http://camel.apache.org/schema/spring"</span><span
class="nt">></span>
 <span
class="nt"><route></span>
 <span
class="nt"><from</span> <span class="na">uri=</span><span
class="s">"jms:queue:start"</span><span
class="nt">/></span>
 <span class="nt"><to</span> <span
class="na">uri=</span><span class="s">"mock:result"</span><span
class="nt">/></span>
 <span
class="nt"></route></span>
 <span
class="nt"></camelContext></span>

 <span
class="c"><!-- This bean will import use the OSGi service from the context
above --></span>
 <span class="nt"><bean</span> <span
class="na">id=</span><span class="s">"jms"</span> <span
class="na">class=</span><span
class="s">"org.apache.camel.component.jms.JmsComponent"</span><span
class="nt">></span>�
00A; <span class="nt"><property</span> <span
class="na">name=</span><span class="s">"connectionFactory"</span>
<span class="na">ref=</span><span
class="s">"jmsConnectionPool"</span> <span
class="nt">/></span>
 <span class="c"><!-- If you have a
transaction manager configured</span>
<span class="c">
<property name="transacted" value="true"
/></span>
<span class="c"> <property
name="transactionManager" ref="transactionManager"
/></span>
<span class="c"> --></span>
 <span
class="nt"></bean></span>

<span
class="nt"></beans></span>
</pre></div>
</div>
</div>
</div>
<div id="siteFooter">
- © 2008-2012 The Apache Software Foundation - <a
href="http://servicemix.apache.org/site/privacy-policy.html";>Privacy Policy</a>
+ © 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">
- © 2008-2012 The Apache Software Foundation - <a
href="http://servicemix.apache.org/site/privacy-policy.html";>Privacy Policy</a>
+ © 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">
- © 2008-2012 The Apache Software Foundation - <a
href="http://servicemix.apache.org/site/privacy-policy.html";>Privacy Policy</a>
+ © 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> 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>
-
-<?xml version="1.0" encoding="UTF-8"?>
-<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0"
- xmlns:camel="http://camel.apache.org/schema/blueprint">
-
- <!--
- 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
-
- -->
- <camelContext id="camelContext"
xmlns="http://camel.apache.org/schema/blueprint">
- <packageScan>
-
<package>org.apache.servicemix.examples.activiti</package>
- </packageScan>
- </camelContext>
-
- <!--
- Obtain a reference to Activiti's RuntimeService - this reference will
automatically
- be picked up by the subsequent Activiti Camel component definition
- -->
- <reference id="runtimeService"
interface="org.activiti.engine.RuntimeService" />
-
- <!--
- 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
-
- -->
- <service interface="org.activiti.camel.ContextProvider">
- <bean class="org.activiti.camel.SimpleContextProvider">
- <argument value="OrderProcess"/>
- <argument ref="camelContext"/>
- </bean>
- </service>
-
-</blueprint>
-</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("file:var/activiti-camel/order")
- .setBody(bean(helper))
- .setProperty(PROCESS_KEY_PROPERTY, simple("file:name"))
- .to("activiti:OrderProcess")
- .log("Process to handle incoming order file has been started
(process instance id ${body})");
-
- /*
- * 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("file:var/activiti-camel/delivery")
- .log("Notifying process about delivery for order
${file:name}")
- .setProperty(PROCESS_KEY_PROPERTY, simple("file:name"))
- .to("activiti:OrderProcess:receiveDelivery");
-
- /*
- * 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("activiti:OrderProcess:processOrder")
- .log("Processing order ${property.orderid} created on
${property:timestamp}")
- .log(" original message: ${property.message}");
-
- from("activiti:OrderProcess:processDelivery")
- .log("Processing delivery for order ${property.orderid}
created on ${property:timestamp}")
- .log(" original message: ${property.message}");
- }
-
- /*
- * 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("${date:now:yyyy-MM-dd
kk:mm:ss}") String timestamp) {
- Map<String, Object> variables = new HashMap<String,
Object>();
- variables.put("message", body);
- variables.put("orderid", filename);
- variables.put("timestamp", timestamp);
- return variables;
- }
- }
-}
-</code></pre></div><h3 id="Processdefinition">Process definition</h3><div
class="syntax"><pre name='code' class='brush: xml; gutter: false;'><code>
-
-<definitions xmlns="http://www.omg.org/spec/BPMN/20100524/MODEL"
- xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:activiti="http://activiti.org/bpmn"
- xmlns:bpmndi="http://www.omg.org/spec/BPMN/20100524/DI"
xmlns:omgdc="http://www.omg.org/spec/DD/20100524/DC"
- xmlns:omgdi="http://www.omg.org/spec/DD/20100524/DI"
typeLanguage="http://www.w3.org/2001/XMLSchema"
- expressionLanguage="http://www.w3.org/1999/XPath"
targetNamespace="http://www.activiti.org/test">
-
-
- <process id="OrderProcess"
isExecutable="true">
-
- <startEvent id="start" />
-
- <sequenceFlow id="flow1"
sourceRef="start" targetRef="processOrder" />
-
- <serviceTask id="processOrder"
- activiti:delegateExpression="${camel}" />
-
- <sequenceFlow id="flow2"
sourceRef="processOrder"
- targetRef="receiveDelivery" />
-
- <receiveTask id="receiveDelivery" name="Wait
for Delivery" />
-
- <sequenceFlow id="flow3"
sourceRef="receiveDelivery"
- targetRef="processDelivery" />
-
- <serviceTask id="processDelivery"
- activiti:delegateExpression="${camel}" />
-
- <sequenceFlow id="flow4"
sourceRef="processDelivery"
- targetRef="end" />
-
- <endEvent id="end" />
-
- </process>
-
-</definitions>
-</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 --> processOrder --> waitForDelivery --> processDelivery -->
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>
features:install activiti
</pre></div>
</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.
</pre></div>
</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"><?xml
version="1.0" encoding="UTF-8"?></span>
<span
class="nt"><blueprint</span> <span class="na">xmlns=</span><span
class="s">"http://www.osgi.org/xmlns/blueprint/v1.0.0"</span>

<span class="na">xmlns:camel=</span><span
class="s">"http://camel.apache.org/schema/blueprint"</span><span
class="nt">></span>

 <span
class="c"><!--</span>
<span class="c"> This Camel context
contains the routes that interact with our BPMN process</span>
<span
class="c"> </span>
<span class="c"> Here we instruct the Camel
context to scan the classpath i
n</span>
<span class="c"> org.apache.servicemix.examples.activiti
</span>
<span class="c"> </span>
<span class="c">
--></span>
 <span class="nt"><camelContext</span> <span
class="na">id=</span><span class="s">"camelContext"</span> <span
class="na">xmlns=</span><span
class="s">"http://camel.apache.org/schema/blueprint"</span><span
class="nt">></span>
 <span
class="nt"><packageScan></span>
 <span
class="nt"><package></span>org.apache.servicemix.examples.activiti<span
class="nt"></package></span>
 <span
class="nt"></packageScan></span>
 <span
class="nt"></camelContext></span>

 <span
class="c"><!--</span>
<span class="c"> Obtain a reference to
Activiti's RuntimeService - this reference will
automatically</span>
<span class="c"> be picked up by the
subsequent Activiti Camel component defin
ition</span>
<span class="c"> --></span>
 <span
class="nt"><reference</span> <span class="na">id=</span><span
class="s">"runtimeService"</span> <span
class="na">interface=</span><span
class="s">"org.activiti.engine.RuntimeService"</span> <span
class="nt">/></span>

 <span
class="c"><!--</span>
<span class="c"> Register a context
provider to link the Camel context to the OrderProcess
definition.</span>
<span class="c"> Doing this will allow your
BPMN process to communicate with the Camel routes using the</span>
<span
class="c"> ${camel} expression</span>
<span class="c"> The
definition of SimpleContextProvider allows to connects a deployed process
definition on the Activiti Engine to a Camel context.</span>
<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>

;
<span class="c"> --></span>
 <span
class="nt"><service</span> <span class="na">interface=</span><span
class="s">"org.activiti.camel.ContextProvider"</span><span
class="nt">></span>
 <span class="nt"><bean</span> <span
class="na">class=</span><span
class="s">"org.activiti.camel.SimpleContextProvider"</span><span
class="nt">></span>
 <span class="nt"><argument</span>
<span class="na">value=</span><span
class="s">"OrderProcess"</span><span class="nt">/></span>

<span class="nt"><argument</span> <span
class="na">ref=</span><span class="s">"camelContext"</span><span
class="nt">/></span>
 <span
class="nt"></bean></span>
 <span
class="nt"></service></span>

<span
class="nt"></blueprint></span>
</pre></div>
</div><h3
id="RouteDefinition">Route Definition</h3><div class="syntax"><div cl
ass="highlight"><pre><span class="cm">/**</span>
<span class="cm"> *
Camel routes that interact with the business process defined in
the</span>
<span class="cm"> * OSGI-INF/activiti/OrderProcess.bpmn20.xml
file</span>
<span class="cm"> */</span>
<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>

 <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>

 <span
class="nd">@Override</span>
 <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>�
00A; <span class="cm">/*</span>
<span class="cm"> * This
route will start a new OrderProcess instance. Using the PROCESS_KEY_PROPERTY,
we are assigning a</span>
<span class="cm"> * business key to
our process to allow for easier correlation in later processing steps. We are
also</span>
<span class="cm"> * sending a Map containing
additional variables to add to the process instance.</span>
<span
class="cm"> */</span>
 <span class="n">from</span><span
class="o">(</span><span
class="s">"file:var/activiti-camel/order"</span><span
class="o">)</span>
 <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>
 <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">"file:name"</span><span
class="o">))</span>
 <span class="o">.</span><span
class="na">to</span><span class="o">(</span><span
class="s">"activiti:OrderProcess"</span><span
class="o">)</span>
 <span class="o">.</span><span
class="na">log</span><span class="o">(</span><span class="s">"Process to
handle incoming order file has been started (process instance id
${body})"</span><span class="o">);</span>

 <span
class="cm">/*</span>
<span class="cm"> * This route will notify
a running OrderProcess of an order delivery event. Here too, we are setting
the</span>
<span class="cm"> * PROCESS_KEY_PROPERTY to correlate
the delivery message with right order process instance.</span>
<span
class="cm"> */</span>
 <span class="n">from</span><span
class="o">(</span><sp
an class="s">"file:var/activiti-camel/delivery"</span><span
class="o">)</span>
 <span class="o">.</span><span
class="na">log</span><span class="o">(</span><span class="s">"Notifying
process about delivery for order ${file:name}"</span><span
class="o">)</span>
 <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">"file:name"</span><span class="o">))</span>

<span class="o">.</span><span class="na">to</span><span
class="o">(</span><span
class="s">"activiti:OrderProcess:receiveDelivery"</span><span
class="o">);</span>

 <span
class="cm">/*</span>
<span class="cm"> * The BPMN process can
also trigger Camel routes as part of the process. In these routes, the
variables that</span>
<span cl
ass="cm"> * you added to the process are available as Exchange
properties. The next two routes will be triggered while</span>
<span
class="cm"> * processing the order and the order
delivery.</span>
<span class="cm"> */</span>

<span class="n">from</span><span class="o">(</span><span
class="s">"activiti:OrderProcess:processOrder"</span><span
class="o">)</span>
 <span class="o">.</span><span
class="na">log</span><span class="o">(</span><span class="s">"Processing
order ${property.orderid} created on ${property:timestamp}"</span><span
class="o">)</span>
 <span class="o">.</span><span
class="na">log</span><span class="o">(</span><span class="s">" original
message: ${property.message}"</span><span
class="o">);</span>

 <span class="n">from</span><span
class="o">(</span><span
class="s">"activiti:OrderProcess:processDelivery"</span><span cla
ss="o">)</span>
 <span class="o">.</span><span
class="na">log</span><span class="o">(</span><span class="s">"Processing
delivery for order ${property.orderid} created on
${property:timestamp}"</span><span class="o">)</span>

<span class="o">.</span><span class="na">log</span><span
class="o">(</span><span class="s">" original message:
${property.message}"</span><span class="o">);</span>
 <span
class="o">}</span>

 <span class="cm">/*</span>
<span
class="cm"> * A few helper methods used for routing</span>
<span
class="cm"> */</span>
 <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>

 <span
class="cm">/*</span>
<span class="cm"> * This method will
extract information from the Exchange (using Camel annotations)
and put them in a</span>
<span class="cm"> * Map that will be
used for setting up the process' variables.</span>
<span class="cm">
*/</span>
 <span class="nd">@Handler</span>

<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>

<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>
 <span
class="nd">@Simple</span><span class="o">(</span><span
class="s">"${date:now:yyyy-MM-dd kk:mm:ss}"</span><span
class="o">)</span> <span class="n">String</span>
<span class="n">timestamp</span><span class="o">)</span> <span
class="o">{</span>
 <span class="n">Map</span><span
class="o"><</span><span class="n">String</span><span class="o">,</span>
<span class="n">Object</span><span class="o">></span> <span
class="n">variables</span> <span class="o">=</span> <span class="k">new</span>
<span class="n">HashMap</span><span class="o"><</span><span
class="n">String</span><span class="o">,</span> <span
class="n">Object</span><span class="o">>();</span>
 <span
class="n">variables</span><span class="o">.</span><span
class="na">put</span><span class="o">(</span><span
class="s">"message"</span><span class="o">,</span> <span
class="n">body</span><span class="o">);</span>
 <span
class="n">variables</span><span class="o">.</span><span
class="na">put</span><span class="o">(</span><span
class="s">"orderid"</span><span class="o">,</span> <span
class="n">filename</span><span
class="o">);</span>
 <span class="n">variables</span><span
class="o">.</span><span class="na">put</span><span class="o">(</span><span
class="s">"timestamp"</span><span class="o">,</span> <span
class="n">timestamp</span><span class="o">);</span>
 <span
class="k">return</span> <span class="n">variables</span><span
class="o">;</span>
 <span class="o">}</span>
 <span
class="o">}</span>
<span
class="o">}</span>
</pre></div>
</div><h3
id="Processdefinition">Process definition</h3><div class="syntax"><div
class="highlight"><pre><span class="nt"><definitions</span> <span
class="na">xmlns=</span><span
class="s">"http://www.omg.org/spec/BPMN/20100524/MODEL"</span>

<span class="na">xmlns:xsi=</span><span
class="s">"http://www.w3.org/2001/XMLSchema-instance"</span> <span
class="na">xmlns:activiti=</span><span
class="s">"http://activiti.org/bpmn"</span>
 <sp
an class="na">xmlns:bpmndi=</span><span
class="s">"http://www.omg.org/spec/BPMN/20100524/DI"</span> <span
class="na">xmlns:omgdc=</span><span
class="s">"http://www.omg.org/spec/DD/20100524/DC"</span>

<span class="na">xmlns:omgdi=</span><span
class="s">"http://www.omg.org/spec/DD/20100524/DI"</span> <span
class="na">typeLanguage=</span><span
class="s">"http://www.w3.org/2001/XMLSchema"</span>
 <span
class="na">expressionLanguage=</span><span
class="s">"http://www.w3.org/1999/XPath"</span> <span
class="na">targetNamespace=</span><span
class="s">"http://www.activiti.org/test"</span><span
class="nt">></span>


 <span
class="nt"><process</span> <span class="na">id=</span><span
class="s">"OrderProcess"</span> <span
class="na">isExecutable=</span><span class="s">"true"</span><span
class="nt">></span>

 <span
class="nt"><startEvent</span> <span class
="na">id=</span><span class="s">"start"</span> <span
class="nt">/></span>

 <span
class="nt"><sequenceFlow</span> <span class="na">id=</span><span
class="s">"flow1"</span> <span class="na">sourceRef=</span><span
class="s">"start"</span> <span class="na">targetRef=</span><span
class="s">"processOrder"</span> <span
class="nt">/></span>

 <span
class="nt"><serviceTask</span> <span class="na">id=</span><span
class="s">"processOrder"</span>
 <span
class="na">activiti:delegateExpression=</span><span
class="s">"${camel}"</span> <span
class="nt">/></span>

 <span
class="nt"><sequenceFlow</span> <span class="na">id=</span><span
class="s">"flow2"</span> <span class="na">sourceRef=</span><span
class="s">"processOrder"</span>
 <span
class="na">targetRef=</span><span class="s">"receiveDelivery"</span>
<span class="nt">/></sp
an>

 <span class="nt"><receiveTask</span> <span
class="na">id=</span><span class="s">"receiveDelivery"</span> <span
class="na">name=</span><span class="s">"Wait for Delivery"</span>
<span class="nt">/></span>

 <span
class="nt"><sequenceFlow</span> <span class="na">id=</span><span
class="s">"flow3"</span> <span class="na">sourceRef=</span><span
class="s">"receiveDelivery"</span>

<span class="na">targetRef=</span><span
class="s">"processDelivery"</span> <span
class="nt">/></span>

 <span
class="nt"><serviceTask</span> <span class="na">id=</span><span
class="s">"processDelivery"</span>
 <span
class="na">activiti:delegateExpression=</span><span
class="s">"${camel}"</span> <span
class="nt">/></span>

 <span
class="nt"><sequenceFlow</span> <span class="na">id=</span><span
class="s">"flow4"</span> <span class="
na">sourceRef=</span><span
class="s">"processDelivery"</span>

<span class="na">targetRef=</span><span class="s">"end"</span> <span
class="nt">/></span>

 <span
class="nt"><endEvent</span> <span class="na">id=</span><span
class="s">"end"</span> <span class="nt">/></span>


<span class="nt"></process></span>

<span
class="nt"></definitions></span>
</pre></div>
</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 --> processOrder -->
waitForDelivery --> processDelivery --> end

</pre></div>
</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">
- © 2008-2012 The Apache Software Foundation - <a
href="http://servicemix.apache.org/site/privacy-policy.html";>Privacy Policy</a>
+ © 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">
- © 2008-2012 The Apache Software Foundation - <a
href="http://servicemix.apache.org/site/privacy-policy.html";>Privacy Policy</a>
+ © 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">
- © 2008-2012 The Apache Software Foundation - <a
href="http://servicemix.apache.org/site/privacy-policy.html";>Privacy Policy</a>
+ © 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>
