Mailing-List: contact camel-dev-help@activemq.apache.org; run by ezmlm
Precedence: bulk
Reply-To: camel-dev@activemq.apache.org
Received-SPF: pass (athena.apache.org: domain of email.wtam@gmail.com
 designates 64.233.166.179 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=c/oDGGdEb0sQxCFye+VaAi6D/c55byZxGJFDPu+JNOnXV4/2pmkdrQdaPSEeUrUx7PicODTREA2b69sTh9m6s2E4plp7m4pEIdChRa1jTK1E7fFwq11uJ+o4Dy7YFFuaPPI7FEMHLgPHK0XqXcuek7u2ajWx4KOXztTvMbPPf/c=
Message-ID: <eeacbf0c0710071438u9fbf3adna6ab32312211cf83@mail.gmail.com>
Date: Sun, 7 Oct 2007 17:38:31 -0400
From: "William Tam" <email.wtam@gmail.com>
To: camel-dev@activemq.apache.org
Subject: Re: a few comments on SedaComponent
In-Reply-To: <af2843cd0710051315n3a8a75aelf8e106cb7fed16b4@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <eeacbf0c0710041555q13f2e541t70054bcbad770b6f@mail.gmail.com>
	 <af2843cd0710042028p4a7931cfrc58473d9db17b605@mail.gmail.com>
	 <eeacbf0c0710051210y55fa9194s2a70486e7fd45bb6@mail.gmail.com>
	 <af2843cd0710051315n3a8a75aelf8e106cb7fed16b4@mail.gmail.com>

> >
> > BTW, I think if the callback passes me the processed exchange, there
> > would be super nice.  I probably care more about out message (if any)
> > than whether it has been done synchronously or not.
> >
>
> Since the caller of the asyc process call passes in the exchange, he
> can pass that same exchange to the call back via either injection or
> via final local reference.  Something like:
>
> final Exchange exch = ...
> processor.process(exch, new AsyncCallback() {
>   public void done(boolean sync) {
>      System.out.println( exch.getOut() );
>   }
> });
>

Actually, this technique does not work for any component producer that
makes a copy of the exchange.  For example, the seda producer makes a
copy of an exchange and endqueue the copy.

        public boolean process(Exchange exchange, AsyncCallback callback) {
            queue.add(exchange.copy());
            callback.done(true);
            return true;
        }

Then, the seda consumer thread could update (in, out, fault) messages
in the copied exchange but any update can not be seen in the orginal
exchange (as in your example).