----- Original Message -----
From: "David Linker" <email@hidden>
To: <email@hidden>
Sent: Thursday, December 16, 2004 2:28 PM
Subject: How do I debug "old interface" errors?
> I am trying to write an applet which will use one interface when
> running on a Swing-enabled browser, and another (AWT) on others that do
> not have swing.
Fwiw my application also has it's gui set up this way. Probably going back
to 1.1 when Swing availability was more questionable and Swing itself was
less usable. Now mostly I use Swing and probably don't always keep the AWT
side of things updated.
Anyhow, for debugging. A ClassNotFound or something like that is probably
not real helpful as far as a stack crawl but the error stack crawl should be
checked to see if it tells you anything.
Verbose class loading might be difficult to arrange from a browser as well.
I'm not sure how you stepped through XCode but running your code through
some class dependancy tool might be better at locating the Swing class. My
application includes a 'depends'/'depend' command pair I got somewhere that
serve this function. Anything with a class browser might as well, the Jode
disassembler I think might include a class browser.
Serialization can be a pretty good dependancy checker as well. You can
subclass ObjectOutputStream overriding a couple methods where you can check
what class is being serialized and output debug messages. My code has a
CustomObjectOutputStream that I use in this way.
If you can run or boot classic you can actually test yourself without Swing
might make it easier to recreate.
Mike Hall mikehall at spacestar dot net
http://www.spacestar.net/users/mikehall
_______________________________________________
Do not post admin requests to the list. They will be ignored.
Java-dev mailing list (email@hidden)
Help/Unsubscribe/Update your Subscription:
http://lists.apple.com/mailman/options/java-dev/email@hidden
This email sent to email@hidden
