🚀 go-pugleaf

I have a JavaBean (heavily based on Swing) with a .ser file
that is serialized using JDK1.2.2-04 on Solaris 2.6.
(The version of JDK shipped with JBuilder 3 Foundation
for Solaris.)

I can deploy this JavaBean in JBuilder 3 Professional Edition's
pallette using Target JDK as JDK1.2.2 (the version
of JDK shipped with JBuiulder 3 Foundation edition for Windows
NT).

When I drag and drop this bean into an application
being designed within JBuilder 3 PE, using Target JDK as 1.2.2,
on Windows NT, the bean does not initialize itself from the
.ser file, when working looking at it under
the Design tab. However, when I run the application,
with Beans.instaniate option for coding, the application
runs fine, and displays the bean properly initialized from
its .ser file.



I also noticed that this bean
does not initialize itself from the .ser file
 when I deploy this bean in JBuilder 3 Foundation
(Target JDK 1.2.2), when looking under the design tab,
but, as in the case of JBuilder 3 PE, the application
runs fine and shows the bean correctly initialized.

One more data point:
When I serialize the same bean using JDK1.2.1-04 on Solaris,
and use it in JBuilder 3 PE on Windows NT, with Target JDK set to 
JDK 1.2 (shipped with Jbuilder 3 PE), the bean shows
up fine under the Design tab and also the application
works fine.

Why is it that a bean serailzed with JDK 1.2.2 and deployed
using Target JDK 1.2.2 does not  initialize itself
under the design tab, but does so when the application
is run? Is it because the version of Target JDK selected
is not really used by JBuilder for its internal use for
shwoing beans in the design tab.