... obviously not of great concern to people then... :wistle: I was thinking more on this though... would it not be better to declare a ProcessorException class that extends Exception and let it wrap any other exception. The Processor process prototype could then declare that it throws ProcessorException instead of Exception. That way you could still have your IDE flag potential exception handling and if you don't care about the exception, catch it and re-throw as a ProcessorException...
Any thoughts on this or am I the only one who has been caught out so far? -- View this message in context: http://www.nabble.com/Processor-throws-clause-side-effects-tp19877248s22882p19930781.html Sent from the Camel - Users mailing list archive at Nabble.com.
