Michael Brown September 9 2010 04:59:24 AMAs Bob Balaban, who did the pioneering work on this subject, said, this one just keeps on coming back. Well over ten years after the introduction of Java into Notes/Domino, the product sill has no built-in debugger.
The solution, it seems, is to use a debugging facilities of an external product, such as eclipse. I've spend all day trying to get this to work, and the screenshot below is proof that yes, it can be done!
There's quite a few posts around the interweb that explain how to set it all up. None of them are a definitive how-to, IMHO, so I may put together one of my own. I worked it out by pinching bit and bobs from various of those posts, and I am, in particular, indebted to the aforementioned Mr Balaban. (Google for him or search Planet Lotus.)
I've got it stepping though the code line by line, in and out of (my own) classes, and displaying the status and values for various variables at any stage.
My main disappointment, so far, is that the debugger doesn't really show much in they way of properties for the built-in Domino objects. For example, check again the screen shot above; the currentDB object is of Domino Java's Database class (which is, of course, the equivalent of LotusScript's NotesDatabase class). And yet, it has only a small number of properties that show in the debugger's Variables tab, and they don't look much like Domino properties either. I mean, what exactly is a "weakObject", I wonder?
I don't know if this because of step that I missed or maybe that's just all you can expect from an external debugger. Answers welcome! I'll add it to the up coming how-to post.
- Comments