No, a breakpoint stops the execution in the caught StackFrame at the position the breakpoint was set and triggered. After that, you can either continue stepping through manually line-by-line deciding if you either go into the execution of the given line or step over it (you can also step back - out of the method you are currently at). Or you could skip to the next breakpoint.
But if you make any changes, the code has to recompile and the server has to restart for your changes to take effect.
A more enterprise approach would be to write unit tests for the bits and pieces you tinker with and test them in isolation. Depending on the number of dependencies it could mean runtime of milliseconds up to a couple of seconds. Take a look at Test-Driven-Development.
发布评论
评论（1）
不，断点停止了在设置并触发断点的位置捕获的stackframe中的执行。之后，您可以继续逐步逐步逐步决定是否进入给定行的执行或逐步执行（您也可以退后 - 从当前使用的方法中退出）。或者您可以跳到下一个断点。
但是，如果进行任何更改，则代码必须重新编译，并且服务器必须重新启动才能进行更改才能生效。
一种更具企业的方法是为您修补的零件编写单元测试，然后孤立地对其进行测试。
根据依赖的数量，这可能意味着毫秒至几秒钟的运行时间。看看 test-test-test-driven-develoverment 。
开始编写测试永远不会太晚。 ）
No, a breakpoint stops the execution in the caught StackFrame at the position the breakpoint was set and triggered. After that, you can either continue stepping through manually line-by-line deciding if you either go into the execution of the given line or step over it (you can also step back - out of the method you are currently at). Or you could skip to the next breakpoint.
But if you make any changes, the code has to recompile and the server has to restart for your changes to take effect.
A more enterprise approach would be to write unit tests for the bits and pieces you tinker with and test them in isolation.
Depending on the number of dependencies it could mean runtime of milliseconds up to a couple of seconds. Take a look at Test-Driven-Development.
It is never too late to start writing tests. ;)