svn commit: r949819 - in /servicemix/documentation/trunk/docs: jbi/src/confluence/servicemix-camel.wiki pom.xml

[ge...@apache.org]

Author: gertv
Date: Mon May 31 17:54:02 2010
New Revision: 949819

URL: http://svn.apache.org/viewvc?rev=949819&view=rev
Log:
Set language on the {code} block in servicemix-camel.wiki

Modified:
    servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki
    servicemix/documentation/trunk/docs/pom.xml

Modified: servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki?rev=949819&r1=949818&r2=949819&view=diff
==============================================================================
--- servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki (original)
+++ servicemix/documentation/trunk/docs/jbi/src/confluence/servicemix-camel.wiki Mon May 31 17:54:02 2010
@@ -7,7 +7,7 @@ h3. Namespace and camel-context.xml
 When creating a servicemix-camel service unit, we reuse the default Camel namespace {{http://camel.apache.org/schema/spring}}.
 
 This is an example {{camel-context.xml}} which uses the Spring DSL to define the Camel routes
-{code}
+{code:lang=xml}
 <?xml version="1.0" encoding="UTF-8"?>
 <beans xmlns="http://www.springframework.org/schema/beans"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -27,7 +27,7 @@ This is an example {{camel-context.xml}}
 {code}
 
 It is also possible to use the Java DSL inside a servicemix-camel service unit by referring to the package that contains the {{RouteBuilder}} classes.  An example: this {{camel-context.xml}} file will activate all routes defined by {{RouteBuilder}}s in the {{org.apache.servicemix.example.camel}} package.
-{code}
+{code:lang=xml}
 <?xml version="1.0" encoding="UTF-8"?>
 <beans xmlns="http://www.springframework.org/schema/beans"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
@@ -48,12 +48,12 @@ h2. URI
 Camel routes use URIs to interact with the ESB.  You can use these URIs to expose new endpoints on the ESB as well as to send message exchanges to existing endpoints.
 
 The snippet below automatically exposes a new endpoint to the bus, where the service QName is {{{http://foo.bar.org}MyService}} and the endpoint name is {{MyEndpoint}}.
-{code}
+{code:lang=java}
 from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
 {code}
 
 When a JBI endpoint appears at the end of a route, as in the example below, that will send 
-{code}
+{code:lang=java}
 to("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
 {code}
 
@@ -111,7 +111,7 @@ jbi:endpoint:urn:foo:bar:MyService:MyEnd
 h2. Example routes
 h3. Simple Spring route
 This simple Spring route registers a new endpoint on the ESB (service {{{urn:org:example}Router}}, endpoint name {{orders}}).  The message exchange contents will be logged and then forwarded to another JBI service endpoint (service {{{http://services.example.org}OrderService}})
-{code}
+{code:lang=xml}
 <beans xmlns="http://www.springframework.org/schema/beans"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="
@@ -133,7 +133,7 @@ This simple Spring route registers a new
 
 h3. The same route using the Java DSL
 When we implement the same route in the Java DSL, we first code our {{RouteBuilder}} implementation
-{code}
+{code:lang=java}
 package org.apache.servicemix.example;
 
 import org.apache.camel.builder.RouteBuilder;
@@ -150,7 +150,7 @@ public class JbiRouteBuilder extends Rou
 {code}
 
 In our {{camel-context.xml}} file, we just refer to the {{org.apache.servicemix.example}} package that contains our {{JbiRouteBuilder}}.
-{code}
+{code:lang=xml}
 <beans xmlns="http://www.springframework.org/schema/beans"
        xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
        xsi:schemaLocation="
@@ -178,8 +178,10 @@ h2. Special considerations
 h3. Stream handling
 If you are using a stream type as the message body, you should be aware that a stream is only capable of being read once. So if you enable {{DEBUG}} logging, the body is usually logged and thus read. To deal with this, Camel has a {{streamCaching}} option that can cache the stream, enabling you to read it multiple times.
 
-{code}
-from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint").streamCaching().to("xslt:transform.xsl", "bean:doSomething");
+{code:lang=java}
+from("jbi:endpoint:http://foo.bar.org/MyService/MyEndpoint")
+  .streamCaching()
+  .to("xslt:transform.xsl", "bean:doSomething");
 {code}
 
 Camel will cache large input streams (by default, over 64K) in a {{temp}} file using {{CachedOutputStream}}. When you close the input stream, the temp file will be deleted.

Modified: servicemix/documentation/trunk/docs/pom.xml
URL: http://svn.apache.org/viewvc/servicemix/documentation/trunk/docs/pom.xml?rev=949819&r1=949818&r2=949819&view=diff
==============================================================================
--- servicemix/documentation/trunk/docs/pom.xml (original)
+++ servicemix/documentation/trunk/docs/pom.xml Mon May 31 17:54:02 2010
@@ -67,7 +67,7 @@
           </execution>
         </executions>
         <configuration>
-          <encoding>UTF-8</encoding>
+          <encoding>UTF-8</encoding>                                                                                                           sv
         </configuration>
       </plugin>
       
@@ -150,7 +150,6 @@
             <configuration>
               <highlightSource>1</highlightSource>
               <highlightDefaultLanguage>xml</highlightDefaultLanguage>
-              <hyphenateVerbatim>1</hyphenateVerbatim>
               <foCustomization>${project.build.directory}/common/styles/docbook-fo.xsl</foCustomization>
               <targetDirectory>${project.reporting.outputDirectory}/pdf</targetDirectory>
             </configuration>