>>> A common issue with Camel is there are often many threads and inputs >>> all processing concurrently and breakpoints can fire at any point in >>> any route which can be confusing. I wonder if we could add some kind >>> of 'flow' conditional method, so we could let the IDE stop at a common >>> breakpoint but it would only fire subsequently for one complete flow >>> through the route until we told the runtime to 'continue'. Kinda like >>> a virtual 'step' operation. >>> >>> e.g. imagine we had a isFlowMessage() function we could use as a >>> conditional breakpoint we set in the IDE. This method returns true for >>> the first invocation; a header is added to the message; it then >>> returns false for all other invocations until its the next step in the >>> flow for the original message. Then it'd be much easier to 'step >>> through' camel routes. >>>
Yeah of course just let the IDE do the conditional breakpoints. We should just make it easier for it having the short name and a few other infos easily avail for it. Good idea. -- Claus Ibsen Apache Camel Committer Author of Camel in Action: http://www.manning.com/ibsen/ Open Source Integration: http://fusesource.com Blog: http://davsclaus.blogspot.com/ Twitter: http://twitter.com/davsclaus
