camel-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From acosent...@apache.org
Subject camel git commit: Added blueprint and spring dsl to Gitbook index
Date Tue, 19 Jul 2016 09:32:27 GMT
Repository: camel
Updated Branches:
  refs/heads/master e148a9c1e -> 421c6bfe1


Added blueprint and spring dsl to Gitbook index


Project: http://git-wip-us.apache.org/repos/asf/camel/repo
Commit: http://git-wip-us.apache.org/repos/asf/camel/commit/421c6bfe
Tree: http://git-wip-us.apache.org/repos/asf/camel/tree/421c6bfe
Diff: http://git-wip-us.apache.org/repos/asf/camel/diff/421c6bfe

Branch: refs/heads/master
Commit: 421c6bfe1b6dad8c44b682d4f6e2db49e0204eca
Parents: e148a9c
Author: Andrea Cosentino <ancosen@gmail.com>
Authored: Tue Jul 19 11:31:39 2016 +0200
Committer: Andrea Cosentino <ancosen@gmail.com>
Committed: Tue Jul 19 11:31:39 2016 +0200

----------------------------------------------------------------------
 docs/user-manual/en/SUMMARY.md                  |  2 +
 .../en/using-osgi-blueprint-with-camel.adoc     | 63 ++++++++++++++++++++
 2 files changed, 65 insertions(+)
----------------------------------------------------------------------


http://git-wip-us.apache.org/repos/asf/camel/blob/421c6bfe/docs/user-manual/en/SUMMARY.md
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/SUMMARY.md b/docs/user-manual/en/SUMMARY.md
index 539ab1d..59eef2f 100644
--- a/docs/user-manual/en/SUMMARY.md
+++ b/docs/user-manual/en/SUMMARY.md
@@ -19,6 +19,8 @@
     * [Dozer Type Conversion](dozer-type-conversion.adoc)
     * [DSL](dsl.adoc)
         * [Java DSL](java-dsl.adoc)
+        * [Spring DSL](spring.adoc)
+        * [Blueprint DSL](using-osgi-blueprint-with-camel.adoc)
         * [Groovy DSL](groovy-dsl.adoc)
         * [Scala DSL](scala-dsl.adoc)
             * [Scala DSL Getting Started](scala-dsl-getting-started.adoc)

http://git-wip-us.apache.org/repos/asf/camel/blob/421c6bfe/docs/user-manual/en/using-osgi-blueprint-with-camel.adoc
----------------------------------------------------------------------
diff --git a/docs/user-manual/en/using-osgi-blueprint-with-camel.adoc b/docs/user-manual/en/using-osgi-blueprint-with-camel.adoc
new file mode 100644
index 0000000..5ee6da6
--- /dev/null
+++ b/docs/user-manual/en/using-osgi-blueprint-with-camel.adoc
@@ -0,0 +1,63 @@
+[[UsingOSGiblueprintwithCamel-UsingOSGiblueprintwithCamel]]
+Using OSGi blueprint with Camel
+~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
+
+*Available as of Camel 2.4*
+
+A custom XML namespace for Blueprint has been created to let you
+leverage the nice XML dialect. Given Blueprint custom namespaces are not
+standardized yet, this namespace can only be used on the
+http://incubator.apache.org/aries/[Apache Aries] Blueprint
+implementation, which is the one used by http://karaf.apache.org[Apache
+Karaf].
+
+[[UsingOSGiblueprintwithCamel-Overview]]
+Overview
+^^^^^^^^
+
+The XML schema is mostly the same as the one for Spring, so all the xml
+snippets throughout the documentation referring to Spring XML also apply
+to Blueprint routes.
+
+Here is a very simple route definition using blueprint:
+
+[source,xml]
+-------------------------------------------------------------------
+<blueprint xmlns="http://www.osgi.org/xmlns/blueprint/v1.0.0">
+
+    <camelContext xmlns="http://camel.apache.org/schema/blueprint">
+        <route>
+            <from uri="timer:test" />
+            <to uri="log:test" />
+        </route>
+    </camelContext>
+
+</blueprint>
+-------------------------------------------------------------------
+
+There are a few limitations at this point about the supported xml
+elements (compared to the Spring xml syntax):
+
+* beanPostProcessor are specific to Spring and aren't allowed
+
+However, using blueprint when you deploy your applications in an OSGi
+enviroment has several advantages:
+
+* when upgrading to a new camel version, you don't have to change the
+namespace, as the correct version will be selected based on the camel
+packages that are imported by your bundle
+* no startup ordering issue with respect to the custom namespaces and
+your bundles
+* you can use Blueprint property placeholders, see more at
+link:using-propertyplaceholder.html[Using PropertyPlaceholder]
+
+[[UsingOSGiblueprintwithCamel-Usingcamel-blueprint]]
+Using camel-blueprint
+^^^^^^^^^^^^^^^^^^^^^
+
+To leverage camel-blueprint in OSGi, you only need the Aries Blueprint
+bundle and the camel-blueprint bundle, in addition to camel-core and its
+dependencies.
+
+If you use Karaf, you can use the feature named `camel-blueprint` which
+will install all the required bundles.


Mime
View raw message