1 of 1 people found this helpful
If you're only looking at setting breaks inside of ESB code, I'd just ignore the missing dependencies. I'd create a new project based on the ESB sources, making sure to set the <esb-root-dir>/product directory as my default location. I know some errors will show up, but it shouldn't prohibit you from hitting your breakpoints inside of ESB code.
Where are you setting your breakpoints? It is strange that they are not being hit, because I do this all the time.
Thanks for your answer Tom.
When I tried it I set the breakpoints inside the notifyException method in ActionProcessingPipeline, but exceptions were thrown and the breakpoint was never hit, so I gave up trying it.
Anyway, if you do it this way and it works, maybe I did something wrong so I'll give it another try and come back if I still do not manage to get it working.
That's strange. Make sure you're using the correct source for your distribution, and maybe try setting breaks earlier in the pipeline to try to figure out what's going on there.
Now it worked as expected.
I downloaded the source again from the branch, imported it into eclipse as you suggested, and my breakpoint was hit at the first attempt.
PS: Is there any "Solved" flag in these forums in order to close the issue?