apupier commented on pull request #84: URL: https://github.com/apache/camel-examples/pull/84#issuecomment-1072231239
> I still think Textual Route Debugging is a bad term. It should just be Route Debugging. > > The other thing you may think about is Visual Route Debugging, like hawtio is able to do. > > So I think the terms should be > > * Route Debugging > > * Visual Route Debugging (when using hawtio or tools that are visual) I think "Route debugging" is not precise enough. When using it, it is not clear if we are talking about textual debugging or visual/graphical debugging. Even "textual route debugging" might not be enough precise here as it is more precisely at the Camel Textual DSL level. it would allow to be able to make the distinction with Camel route debugging using "classic" Java (which can be done using Processors or placing specific breakpoints inside camel core java code). -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: commits-unsubscr...@camel.apache.org For queries about this service, please contact Infrastructure at: us...@infra.apache.org
