Mailing-List: contact users-help@camel.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@camel.apache.org
Received-SPF: neutral (athena.apache.org: 216.139.236.26 is neither permitted
 nor denied by domain of blackorangebox@gmail.com)
Date: Fri, 19 Oct 2012 00:24:35 -0700 (PDT)
From: snowindy <blackorangebox@gmail.com>
To: users@camel.apache.org
Message-ID: <1350631475297-5721277.post@n5.nabble.com>
In-Reply-To: 
 <CAGB5yNnivemQXidGWhTssG6O7YMvf2mzMzPBKWbqMznB1uWnvw@mail.gmail.com>
References: <1350571199607-5721248.post@n5.nabble.com>
 <CAGB5yNnivemQXidGWhTssG6O7YMvf2mzMzPBKWbqMznB1uWnvw@mail.gmail.com>
Subject: Re: Camel application design question
MIME-Version: 1.0
Content-Type: text/plain; charset=us-ascii
Content-Transfer-Encoding: 7bit

Like I said, /ProcessError is simply a utility class containing both
exception caught in a certain stage, and a Stage identifier. Stage id will
be used afterwards to identify stage with no pain with string parsing etc./

In general, I try to utilize Camel to build a flexible request-reply route,
so that more steps can be added after with no other changes.
Certainly, all this can easily be implemented in a 'strategy' Java-class,
which chains actions one after another. 

This is why I am asking about the app design.
How would you implement this part?


--
View this message in context: http://camel.465427.n5.nabble.com/Camel-application-design-question-tp5721248p5721277.html
Sent from the Camel - Users mailing list archive at Nabble.com.