🚀 go-pugleaf

In article <361415CE.E74EAAE0@ici.net>, ejs@ici.net says...
> Okay I just installed JDK 1.1.7. Was easy to set up Jbuilder to use it
> and it runs great.
> But now when I try to debug I get the message "Unsupported debugging
> JDK."
> Please tell me that I have just forget to configure some silly option
> somewhere and this
> does not really mean that Jbuilder 2 can't debug 1.1.7 either.
> 
> 
Upon further thought - I know what the deal is.

Currently, there is no concrete debugging API for Java that allows VM's 
to be plugged in/out for debugging purposes.  As such, the only way that 
JBuilder can debug is to use the VM that runs the JBuilder product 
itself.  This means that you can only use the debugger for the JDK that 
ships with JBuilder.  Period.

When Java supports a true debugging API that will allow products like 
JBuilder to write to standard interfaces instead of specific JDK's, then 
switching a JDK in (that also supports that interface) will also mean 
using that same JDK for debugging (or powering the JBuilder visual 
designer, for that matter).

So the text on the box that everyone keeps pointing to should really be 
read as: "Use JDK switching for runtime support against any JDK".  You 
can not use JDK switching for debugging support, visual designer support, 
or any other support inherent in the JBuilder IDE itself.

Tad Frysinger
[TeamB]