🚀 go-pugleaf

Hi All!

There was a message posted by Mr. Richard Wilkman, explaining the problems
when using jdk 1.2 with Jbuilder 2.0x, As I recall the main problem is the
package names used by jdk 1.2 (javax.swing.*).

I wrote a small bean which uses swing components. I was really stuck when
deploying my bean, since I don�t know what JDK the customers who purchase by
bean will be using. So I wrote a small patch. Which basically is bridge
between 1.1.6 and 1.2. The bridge is really simple. Here is a sample

Package com.sun.java.swing.Jframe

Public class Jframe extends javax.swing.Jframe{

 Public Jframe()
{
}
}

With this I was able to deploy by bean, and customers who uses 1.2 can
download the patch and set the classpath to it.

The bean I wrote was relatively small. I don�t know whether this approach
can be adopted for big applications.

The above solution got me thinking�maybe a solution for JBuilder 2.-x +
jdk1.2 problem�. Hmmm?!!

(OK before I begin I know that there are a lot of Java experts out there,
who would have thought about this much earlier, than me. Also, maybe the
solution I�m about to suggest, is not implementable. So excuse me if I sound
really stupid. And If this cannot be implemented, can anyone tell me why)

Ok. Inprise, negotiates with sun and get�s a jdk1.2 version, which has the
earlier package names. This special jdk1.2 version can be integrated into
Jbuilder 2.0x. Inprise puts this on their web, so all the Jbuilder users can
download it.

inprise also develop a new Deployment Wizard, which attaches the Deflector
classes (Bridge classes), to the classes in the current package. (Inprise
put this wizard, also in the web for all to download)

Ok.. first question    Is this stupid ???

Second question, if this cannot be implemented, why ?

Regards

Dillan Fernando
Sri Lanka