🚀 go-pugleaf

Sven,

We too need this fix quickly.  And with all the pressure, Inprise is
bound to provide this fix within a short time after JDK1.2 is
released(JDK1.2 was scheduled to be released yesterday...).

I considered taking Sun's tool that automatically changes
com.sun.java.swing references to javax.swing and pointing it at all of
the JdbSwing source.  But I'd have to go over the license agreement to
make sure that was legal(even as a temporary measure in house), make
sure that JBuilder finds the modified class files before the
JBCL2.0.jar, and then if any bugs that come up in my code I'd quickly
suspect the changes I had done to JdbSwing, etc, etc.

Currently we're doing JDK1.2 based work in JBuilder, but without any
JdbSwing components, and we will convert it to JdbSwing when Inprise
releases the fix.  We're also focusing our time on other work that is
not affected by JDK1.2.

We've been beating Inprise up on this issue, and it will happen.  But
Inprise's policy is not to release it until it is ready.  And that's a
good policy to have.

I realize this isn't much help, but it's what we're doing about it here
in my shop.

-Hopper.


Sven Sass wrote:

> Hello,
>
> it seems like I am not the only one who has encountered the problem
> with the new Swing location within the JDK 1.2.
>
> I am currently working with it and I'd really like to know, if any
> of those who have encountered this problem have found a fix or
> workaround when you
> - have to use JBCL and
> - want to use JDK 1.2 ( the CORBA elements of it to be more
> precise)
>
> Any help highly appreciated,
>
> best regards,
>
> Sven Sass
>
> ps.: please, don't tell me to use visibroker - I know it and I don't
> want it ;)