Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: pass (nike.apache.org: domain of claus.ibsen@gmail.com
 designates 209.85.217.173 as permitted sender)
MIME-Version: 1.0
In-Reply-To: <1348451013762-5719818.post@n5.nabble.com>
References: <1348221034371-5719716.post@n5.nabble.com>
 <1348451013762-5719818.post@n5.nabble.com>
From: Claus Ibsen <claus.ibsen@gmail.com>
Date: Mon, 24 Sep 2012 09:49:34 +0200
Message-ID: 
 <CAGB5yNnQdncF=9ksSQiKzAE0yuHVD_ObjX7duEpiTN+7ASGNNw@mail.gmail.com>
Subject: Re: Correct use of camelproxy?
To: users@camel.apache.org
Content-Type: text/plain; charset=ISO-8859-1

On Mon, Sep 24, 2012 at 3:43 AM, zuff <bhtan1982@live.com> wrote:
> Hi All,
>
>    I managed to get the route to work. However, I did this by annotating
> @Produce(uri="direct:resultProcessor") on the resultProcessor instance
> variable in the controller class. Is it possible to decouple camel from the
> code, and just use the camelContext.xml for configuration?
>

Yes it can be all done in the XML file only. You would need though in
the XML to setup IoC for the proxy by its id, eg
where you need to use it, you need to inject the bean by id
"resultProxy". eg standard spring bean IoC stuff.


> Thanks and Best Regards,
> Zuff
>
>
>
> --
> View this message in context: http://camel.465427.n5.nabble.com/Correct-use-of-camelproxy-tp5719716p5719818.html
> Sent from the Camel - Users mailing list archive at Nabble.com.


-- 
Claus Ibsen
-----------------
Red Hat, Inc.
FuseSource is now part of Red Hat
Email: cibsen@redhat.com
Web: http://fusesource.com
Twitter: davsclaus
Blog: http://davsclaus.com
Author of Camel in Action: http://www.manning.com/ibsen