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 39CB59264 for ; Wed, 11 Apr 2012 04:28:02 +0000 (UTC) Received: (qmail 11026 invoked by uid 500); 11 Apr 2012 04:28:02 -0000 Delivered-To: apmail-camel-commits-archive@camel.apache.org Received: (qmail 10987 invoked by uid 500); 11 Apr 2012 04:28:01 -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 10972 invoked by uid 99); 11 Apr 2012 04:28:01 -0000 Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 11 Apr 2012 04:28:00 +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; Wed, 11 Apr 2012 04:27:57 +0000 Received: from eris.apache.org (localhost [127.0.0.1]) by eris.apache.org (Postfix) with ESMTP id 0C2B72388A56 for ; Wed, 11 Apr 2012 04:27:36 +0000 (UTC) Content-Type: text/plain; charset="utf-8" MIME-Version: 1.0 Content-Transfer-Encoding: 7bit Subject: svn commit: r812290 - in /websites/production/camel/content: book-component-appendix.html book-in-one-page.html cache/main.pageCache file2.html Date: Wed, 11 Apr 2012 04:27:35 -0000 To: commits@camel.apache.org From: buildbot@apache.org X-Mailer: svnmailer-1.0.8-patched Message-Id: <20120411042736.0C2B72388A56@eris.apache.org> Author: buildbot Date: Wed Apr 11 04:27:35 2012 New Revision: 812290 Log: Production update by buildbot for camel Modified: websites/production/camel/content/book-component-appendix.html websites/production/camel/content/book-in-one-page.html websites/production/camel/content/cache/main.pageCache websites/production/camel/content/file2.html Modified: websites/production/camel/content/book-component-appendix.html ============================================================================== --- websites/production/camel/content/book-component-appendix.html (original) +++ websites/production/camel/content/book-component-appendix.html Wed Apr 11 04:27:35 2012 @@ -3954,29 +3954,6 @@ from("file:The body will be a File object that points to the file that was just dropped into the inputdir directory.

-

Read files from a directory and send the content to a jms queue

- -
-
-from("file://inputdir/").convertBodyTo(String.class).to("jms:test.queue")
-
-
- -

By default the file endpoint sends a FileMessage which contains a File object as the body. If you send this directly to the JMS component the JMS message will only contain the File object but not the content. By converting the File to a String, the message will contain the file content which is probably what you want.

- -

The route above using Spring DSL:

-
-
-   <route>
-      <from uri="file://inputdir/"/>
-      <convertBodyTo type="java.lang.String"/>
-      <to uri="jms:test.queue"/>
-   </route>
-
-
- - -

Writing to files

Camel is of course also able to write files, i.e. produce files. In the sample below we receive some reports on the SEDA queue that we process before they are written to a directory.

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 Wed Apr 11 04:27:35 2012 @@ -24125,29 +24125,6 @@ from("file:The body will be a File object that points to the file that was just dropped into the inputdir directory.

-

Read files from a directory and send the content to a jms queue

- -
-
-from("file://inputdir/").convertBodyTo(String.class).to("jms:test.queue")
-
-
- -

By default the file endpoint sends a FileMessage which contains a File object as the body. If you send this directly to the JMS component the JMS message will only contain the File object but not the content. By converting the File to a String, the message will contain the file content which is probably what you want.

- -

The route above using Spring DSL:

-
-
-   <route>
-      <from uri="file://inputdir/"/>
-      <convertBodyTo type="java.lang.String"/>
-      <to uri="jms:test.queue"/>
-   </route>
-
-
- - -

Writing to files

Camel is of course also able to write files, i.e. produce files. In the sample below we receive some reports on the SEDA queue that we process before they are written to a directory.

Modified: websites/production/camel/content/cache/main.pageCache ============================================================================== Binary files - no diff available. Modified: websites/production/camel/content/file2.html ============================================================================== --- websites/production/camel/content/file2.html (original) +++ websites/production/camel/content/file2.html Wed Apr 11 04:27:35 2012 @@ -420,29 +420,6 @@ from("file:The body will be a File object that points to the file that was just dropped into the inputdir directory.

-

Read files from a directory and send the content to a jms queue

- -
-
-from("file://inputdir/").convertBodyTo(String.class).to("jms:test.queue")
-
-
- -

By default the file endpoint sends a FileMessage which contains a File object as the body. If you send this directly to the JMS component the JMS message will only contain the File object but not the content. By converting the File to a String, the message will contain the file content which is probably what you want.

- -

The route above using Spring DSL:

-
-
-   <route>
-      <from uri="file://inputdir/"/>
-      <convertBodyTo type="java.lang.String"/>
-      <to uri="jms:test.queue"/>
-   </route>
-
-
- - -

Writing to files

Camel is of course also able to write files, i.e. produce files. In the sample below we receive some reports on the SEDA queue that we process before they are written to a directory.