Return-Path: 
 <users-return-24124-apmail-camel-users-archive=camel.apache.org@camel.apache.org>
X-Original-To: apmail-camel-users-archive@www.apache.org
Delivered-To: apmail-camel-users-archive@www.apache.org
Received: from mail.apache.org (hermes.apache.org [140.211.11.3])
	by minotaur.apache.org (Postfix) with SMTP id EC8069920
	for <apmail-camel-users-archive@www.apache.org>;
 Sat, 22 Oct 2011 00:48:07 +0000 (UTC)
Received: (qmail 56730 invoked by uid 500); 22 Oct 2011 00:48:07 -0000
Delivered-To: apmail-camel-users-archive@camel.apache.org
Received: (qmail 56694 invoked by uid 500); 22 Oct 2011 00:48:07 -0000
Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
List-Help: <mailto:users-help@camel.apache.org>
List-Unsubscribe: <mailto:users-unsubscribe@camel.apache.org>
List-Post: <mailto:users@camel.apache.org>
List-Id: <users.camel.apache.org>
Reply-To: users@camel.apache.org
Delivered-To: mailing list users@camel.apache.org
Received: (qmail 56686 invoked by uid 99); 22 Oct 2011 00:48:07 -0000
Received: from nike.apache.org (HELO nike.apache.org) (192.87.106.230)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Oct 2011 00:48:07 +0000
X-ASF-Spam-Status: No, hits=2.0 required=5.0
	tests=FREEMAIL_FROM,SPF_NEUTRAL,T_TO_NO_BRKTS_FREEMAIL,URI_HEX
X-Spam-Check-By: apache.org
Received-SPF: neutral (nike.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of pkleczka@gmail.com)
Received: from [216.139.236.26] (HELO sam.nabble.com) (216.139.236.26)
    by apache.org (qpsmtpd/0.29) with ESMTP; Sat, 22 Oct 2011 00:48:00 +0000
Received: from [192.168.236.26] (helo=sam.nabble.com)
	by sam.nabble.com with esmtp (Exim 4.72)
	(envelope-from <pkleczka@gmail.com>)
	id 1RHPkR-0005KX-RR
	for users@camel.apache.org; Fri, 21 Oct 2011 17:47:39 -0700
Date: Fri, 21 Oct 2011 17:47:39 -0700 (PDT)
From: pkleczka <pkleczka@gmail.com>
To: users@camel.apache.org
Message-ID: <1319244459844-4926428.post@n5.nabble.com>
In-Reply-To: 
 <CAGB5yNkO4v+_VnhzLZ4NQZgrg-8nDNX7kxv5xwQAzBG26VqLOA@mail.gmail.com>
References: <1318604745992-4902912.post@n5.nabble.com>
 <CAGB5yNniSev=aROCq-Njx_1CkVfSQfuSjfppT2Y+jcCjSbdDQA@mail.gmail.com>
 <CAA99P1Ej9Ff2N-xxS0M5_zjb_m19isMGC1xt4o_Jt7PTy3xmOQ@mail.gmail.com>
 <CAGB5yNkO4v+_VnhzLZ4NQZgrg-8nDNX7kxv5xwQAzBG26VqLOA@mail.gmail.com>
Subject: Re: FTP producer and exception or transaction
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit
X-Virus-Checked: Checked by ClamAV on apache.org

Thanks Claus, I got it working. But have one more question. Page 304 of the
Camel in Action book has a note about using the Direct component for
multiple routes because it says the messages must "be processed in the same
thread context". I am not sure I understand this or how I would alter the
two routes below so that a direct component would tie them together.


       &lt;!-- Validate that we pass Odyssey XSD or send to "rejected" queue
--&gt;
        <route id="EFileBatchRequestSubmit">
            <from
uri="properties:{{queue.efilebatch.request.validatedxsdbusrules}}" />
               &lt;!-- ... some operations here ... --&gt;
	       <to uri="properties:{{queue.efilebatch.request.submitted}}" />
        </route>
        
        &lt;!-- Send to Odyssey ftp --&gt;
        <route id="EFileBatchRequestFTP">
            <from uri="properties:{{queue.efilebatch.request.submitted}}" />
            <transacted ref="PROPAGATION_REQUIRED" />
            <bean ref="formatFTPFileName" method="formatName" />
            <to
uri="properties:{{ftp.efilebatch.request.submitted}}?fileName=${header.JMSCorrelationID}.xml"
/>
            <to uri="properties:{{log.efilebatch.request.submitted}}" />
            <wireTap
uri="properties:{{queue.efilebatch.request.submitted.tap}}" />
        </route>

*Would I do something like the following:*

       &lt;!-- Validate that we pass Odyssey XSD or send to "rejected" queue
--&gt;
        <route id="EFileBatchRequestSubmit">
            <from
uri="properties:{{queue.efilebatch.request.validatedxsdbusrules}}" />
               &lt;!-- ... some operations here ... --&gt;
	       <to uri="properties:{{queue.efilebatch.request.submitted}}" />
               *<to uri="direct:tie" />*
        </route>
        
        &lt;!-- Send to Odyssey ftp --&gt;
        <route id="EFileBatchRequestFTP">
            *<to uri="direct:tie" /> &lt;!-- This replaces the: from
uri="properties:{{queue.efilebatch.request.submitted}}" --&gt;*
            <transacted ref="PROPAGATION_REQUIRED" />
            <bean ref="formatFTPFileName" method="formatName" />
            <to
uri="properties:{{ftp.efilebatch.request.submitted}}?fileName=${header.JMSCorrelationID}.xml"
/>
            <to uri="properties:{{log.efilebatch.request.submitted}}" />
            <wireTap
uri="properties:{{queue.efilebatch.request.submitted.tap}}" />
        </route>


--
View this message in context: http://camel.465427.n5.nabble.com/FTP-producer-and-exception-or-transaction-tp4902912p4926428.html
Sent from the Camel - Users mailing list archive at Nabble.com.