🚀 go-pugleaf

George Van Treeck <gvt@tdl.com> writes:

> The official release version of JDK 1.2 (Java 2) has changed the path
> com.sun.java to javax. Okay. I change the "import com.sun.java..." to
> "import javax..." in about 70 of my files and recompile.  The compile
> fails because the JDK no longer includes the Windows or Motif look and
> feel. Okay. I change it to the Metal look and feel. And everything
> compiles.

Actually, the Windows and Motif L&Fs are still there, but they remain
in com.sun.java.swing.plaf.*, because they're not part of the
extension, but part of Sun's own code in the SDK. It's all in the
"incompatilbilities" doc section.

> However, the program which used to run without error in jdk1.1.6_Borland
> now generates lots of exceptions.  JBuilder does not support debugging
> of Java 1.2, so I have no way of stepping through the code to find out
> what is broke.

What is broken is probably that Borland's Swing-derived classes still
rely on the com.sun.java.swing.* packages.

> 
> The situation gets worse.  I go into the JBuilder Designer and find that
> my JFrame is now a large red rectangle.  Further, it does not allow any
> attributes to be changed, nor allows any subcomponent beans to have
> their attributes changed. Nor are any of the subcomponents visible.

That's because the JFrame created by the wizard/bean menu extends the
com.sun.java.swing.JFrame, not the one found in JDK 1.2.

> JBuilder is a good product and Sun has sort of pulled the rug out from
> under Inprise (and me). I sure hope Inprise can help out the above
> problems quickly (yesterday would be quick enough :-)

Sun has _sort of_ pulled the rug from under everyone :-) but the
"renaming" has been know for half a year at least, so that's no excuse
for them not to anticipate it.