Return-Path: X-Original-To: apmail-camel-commits-archive@www.apache.org Delivered-To: apmail-camel-commits-archive@www.apache.org Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by minotaur.apache.org (Postfix) with SMTP id E2F47D921 for ; Thu, 20 Sep 2012 19:20:17 +0000 (UTC) Received: (qmail 72493 invoked by uid 500); 20 Sep 2012 19:20:17 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 72463 invoked by uid 500); 20 Sep 2012 19:20:17 -0000 Mailing-List: contact commits-help@camel.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: dev@camel.apache.org Delivered-To: mailing list commits@camel.apache.org Received: (qmail 72455 invoked by uid 99); 20 Sep 2012 19:20:17 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Sep 2012 19:20:17 +0000 X-ASF-Spam-Status: No, hits=-2000.0 required=5.0 tests=ALL_TRUSTED X-Spam-Check-By: apache.org Received: from [140.211.11.4] (HELO eris.apache.org) (140.211.11.4) by apache.org (qpsmtpd/0.29) with ESMTP; Thu, 20 Sep 2012 19:20:13 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 44B0B238896F for ; Thu, 20 Sep 2012 19:19:29 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r832612 - in /websites/production/camel/content: book-in-one-page.html book-tutorials.html cache/main.pageCache tutorial-example-reportincident-part1.html Date: Thu, 20 Sep 2012 19:19:28 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120920191929.44B0B238896F@eris.apache.org> Author: buildbot Date: Thu Sep 20 19:19:28 2012 New Revision: 832612 Log: Production update by buildbot for camel Modified: websites/production/camel/content/book-in-one-page.html websites/production/camel/content/book-tutorials.html websites/production/camel/content/cache/main.pageCache websites/production/camel/content/tutorial-example-reportincident-part1.html Modified: websites/production/camel/content/book-in-one-page.html ============================================================================== --- websites/production/camel/content/book-in-one-page.html (original) +++ websites/production/camel/content/book-in-one-page.html Thu Sep 20 19:19:28 2012 @@ -4757,7 +4757,7 @@ Part 5 - Is about how embed Camel with S

Prerequisites

This tutorial uses the following frameworks:

-
  • Maven 2.0.9
  • Apache Camel 2.10.0
  • Apache CXF 2.6.1
  • Spring 3.0.7
+
  • Maven 3.0.4
  • Apache Camel 2.10.0
  • Apache CXF 2.6.1
  • Spring 3.0.7

Note: The sample project can be downloaded, see the resources section.

@@ -4884,16 +4884,16 @@ mvn archetype:create -DgroupId=org.apach

CXF wsdl2java

Then we integration the CXF wsdl2java generator in the pom.xml so we have CXF generate the needed POJO classes for our webservice contract.
-However at first we must configure maven to live in the modern world of Java 1.5 so we must add this to the pom.xml

+However at first we must configure maven to live in the modern world of Java 1.6 so we must add this to the pom.xml

-			<!-- to compile with 1.5 -->
+			<!-- to compile with 1.6 -->
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-compiler-plugin</artifactId>
 				<configuration>
-					<source>1.5</source>
-					<target>1.5</target>
+					<source>1.6</source>
+					<target>1.6</target>
 				</configuration>
 			</plugin>
 
@@ -5045,14 +5045,9 @@ The address attribute defines the

To test if we are home free we run mvn clean compile.

Running our webservice

-

Now that the code compiles we would like to run it in a web container, so we add jetty to our pom.xml so we can run mvn jetty:run:

+

Now that the code compiles we would like to run it inside a web container, for this purpose we make use of Jetty which we will bootstrap using it's plugin org.mortbay.jetty:maven-jetty-plugin:

-	<properties>
-             ...
-             <jetty-version>6.1.1</jetty-version>
-	</properties>
-
        <build>
            <plugins>
                ...
@@ -5064,7 +5059,7 @@ The address attribute defines the
                </plugin>
 
-

Notice: We use Jetty v6.1.1 as never versions has troubles on my laptop. Feel free to try a newer version on your system, but v6.1.1 works flawless.

+

Notice: We make use of the Jetty version being defined inside the Camel's Parent POM.

So to see if everything is in order we fire up jetty with mvn jetty:run and if everything is okay you should be able to access http://localhost:8080.
Jetty is smart that it will list the correct URI on the page to our web application, so just click on the link. This is smart as you don't have to remember the exact web context URI for your application - just fire up the default page and Jetty will help you.

Modified: websites/production/camel/content/book-tutorials.html ============================================================================== --- websites/production/camel/content/book-tutorials.html (original) +++ websites/production/camel/content/book-tutorials.html Thu Sep 20 19:19:28 2012 @@ -598,7 +598,7 @@ Part 5 - Is about how embed Camel with S

Prerequisites

This tutorial uses the following frameworks:

-
  • Maven 2.0.9
  • Apache Camel 2.10.0
  • Apache CXF 2.6.1
  • Spring 3.0.7
+
  • Maven 3.0.4
  • Apache Camel 2.10.0
  • Apache CXF 2.6.1
  • Spring 3.0.7

Note: The sample project can be downloaded, see the resources section.

@@ -725,16 +725,16 @@ mvn archetype:create -DgroupId=org.apach

CXF wsdl2java

Then we integration the CXF wsdl2java generator in the pom.xml so we have CXF generate the needed POJO classes for our webservice contract.
-However at first we must configure maven to live in the modern world of Java 1.5 so we must add this to the pom.xml

+However at first we must configure maven to live in the modern world of Java 1.6 so we must add this to the pom.xml

-			<!-- to compile with 1.5 -->
+			<!-- to compile with 1.6 -->
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-compiler-plugin</artifactId>
 				<configuration>
-					<source>1.5</source>
-					<target>1.5</target>
+					<source>1.6</source>
+					<target>1.6</target>
 				</configuration>
 			</plugin>
 
@@ -886,14 +886,9 @@ The address attribute defines the

To test if we are home free we run mvn clean compile.

Running our webservice

-

Now that the code compiles we would like to run it in a web container, so we add jetty to our pom.xml so we can run mvn jetty:run:

+

Now that the code compiles we would like to run it inside a web container, for this purpose we make use of Jetty which we will bootstrap using it's plugin org.mortbay.jetty:maven-jetty-plugin:

-	<properties>
-             ...
-             <jetty-version>6.1.1</jetty-version>
-	</properties>
-
        <build>
            <plugins>
                ...
@@ -905,7 +900,7 @@ The address attribute defines the
                </plugin>
 
-

Notice: We use Jetty v6.1.1 as never versions has troubles on my laptop. Feel free to try a newer version on your system, but v6.1.1 works flawless.

+

Notice: We make use of the Jetty version being defined inside the Camel's Parent POM.

So to see if everything is in order we fire up jetty with mvn jetty:run and if everything is okay you should be able to access http://localhost:8080.
Jetty is smart that it will list the correct URI on the page to our web application, so just click on the link. This is smart as you don't have to remember the exact web context URI for your application - just fire up the default page and Jetty will help you.

Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/tutorial-example-reportincident-part1.html ============================================================================== --- websites/production/camel/content/tutorial-example-reportincident-part1.html (original) +++ websites/production/camel/content/tutorial-example-reportincident-part1.html Thu Sep 20 19:19:28 2012 @@ -79,7 +79,7 @@

Prerequisites

This tutorial uses the following frameworks:

-
  • Maven 2.0.9
  • Apache Camel 2.10.0
  • Apache CXF 2.6.1
  • Spring 3.0.7
+
  • Maven 3.0.4
  • Apache Camel 2.10.0
  • Apache CXF 2.6.1
  • Spring 3.0.7

Note: The sample project can be downloaded, see the resources section.

@@ -206,16 +206,16 @@ mvn archetype:create -DgroupId=org.apach

CXF wsdl2java

Then we integration the CXF wsdl2java generator in the pom.xml so we have CXF generate the needed POJO classes for our webservice contract.
-However at first we must configure maven to live in the modern world of Java 1.5 so we must add this to the pom.xml

+However at first we must configure maven to live in the modern world of Java 1.6 so we must add this to the pom.xml

-			<!-- to compile with 1.5 -->
+			<!-- to compile with 1.6 -->
 			<plugin>
 				<groupId>org.apache.maven.plugins</groupId>
 				<artifactId>maven-compiler-plugin</artifactId>
 				<configuration>
-					<source>1.5</source>
-					<target>1.5</target>
+					<source>1.6</source>
+					<target>1.6</target>
 				</configuration>
 			</plugin>
 
@@ -367,14 +367,9 @@ The address attribute defines the

To test if we are home free we run mvn clean compile.

Running our webservice

-

Now that the code compiles we would like to run it in a web container, so we add jetty to our pom.xml so we can run mvn jetty:run:

+

Now that the code compiles we would like to run it inside a web container, for this purpose we make use of Jetty which we will bootstrap using it's plugin org.mortbay.jetty:maven-jetty-plugin:

-	<properties>
-             ...
-             <jetty-version>6.1.1</jetty-version>
-	</properties>
-
        <build>
            <plugins>
                ...
@@ -386,7 +381,7 @@ The address attribute defines the
                </plugin>
 
-

Notice: We use Jetty v6.1.1 as never versions has troubles on my laptop. Feel free to try a newer version on your system, but v6.1.1 works flawless.

+

Notice: We make use of the Jetty version being defined inside the Camel's Parent POM.

So to see if everything is in order we fire up jetty with mvn jetty:run and if everything is okay you should be able to access http://localhost:8080.
Jetty is smart that it will list the correct URI on the page to our web application, so just click on the link. This is smart as you don't have to remember the exact web context URI for your application - just fire up the default page and Jetty will help you.