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.
