From 3d22972466417a66af28303e49f8b1beae78a752 Mon Sep 17 00:00:00 2001
From: Paolo Antinori <pantinor@redhat.com>
Date: Tue, 22 Nov 2016 17:43:27 +0100
Subject: [PATCH] KEYCLOAK-3678 - Docs - Added Camel RestDSL

---
 topics/oidc/java/fuse/camel.adoc | 60 ++++++++++++++++++++++++++++++++
 1 file changed, 60 insertions(+)

diff --git a/topics/oidc/java/fuse/camel.adoc b/topics/oidc/java/fuse/camel.adoc
index 1cd7a21564..324c912bb7 100644
--- a/topics/oidc/java/fuse/camel.adoc
+++ b/topics/oidc/java/fuse/camel.adoc
@@ -93,3 +93,63 @@ org.osgi.service.blueprint.container,
 org.osgi.service.event,
 ----
 
+===== Camel RestDSL
+
+Camel RestDSL is a Camel feature to define your REST endpoints in a fluent way.
+But under the hood, the capability to provide all this magic, is still demanded to specific implementation classes and
+you have to instruct them on how to integrate with Keycloak.
+
+The way to configure the integration mechanism depends on the Camel component that you configure your RestDSL defined routes to work with.
+
+This is an example that show how to do it while using Jetty engine, with reference to some beans defined in the example above.
+
+[source,xml]
+----
+<bean id="securityHandlerRest" class="org.eclipse.jetty.security.ConstraintSecurityHandler">
+    <property name="authenticator" ref="keycloakAuthenticator" />
+    <property name="constraintMappings">
+        <list>
+            <ref component-id="constraintMapping" />
+        </list>
+    </property>
+    <property name="authMethod" value="BASIC"/>
+    <property name="realmName" value="does-not-matter"/>
+</bean>
+
+<bean id="sessionHandlerRest" class="org.keycloak.adapters.jetty.spi.WrappingSessionHandler">
+    <property name="handler" ref="securityHandlerRest" />
+</bean>
+
+
+<camelContext id="blueprintContext"
+              trace="false"
+              xmlns="http://camel.apache.org/schema/blueprint">
+
+    <restConfiguration component="jetty" contextPath="/restdsl"
+                       port="8484">
+        <!--the link with Keycloak security handlers happens here-->
+        <endpointProperty key="handlers" value="sessionHandlerRest"></endpointProperty>
+        <endpointProperty key="matchOnUriPrefix" value="true"></endpointProperty>
+    </restConfiguration>
+
+    <rest path="/hello" >
+        <description>Hello rest service</description>
+        <get uri="/{id}" outType="java.lang.String">
+            <description>Just an helllo</description>
+            <to uri="direct:justDirect" />
+        </get>
+
+    </rest>
+
+    <route id="justDirect">
+        <from uri="direct:justDirect"/>
+        <process ref="helloProcessor" />
+        <log message="RestDSL correctly invoked ${body}"/>
+        <setBody>
+            <constant>(__This second sentence is returned from a Camel RestDSL endpoint__)</constant>
+        </setBody>
+    </route>
+
+</camelContext>
+
+---