We had an interesting situation in Store. A class that the image has defined in a package, Store shows as 'not defined' in that same package. The class is then 'unloadable' when the package is loaded into a new image. However, when loading into current image with an old definition of the class, there is no indication of a problem since the class was previously defined.
To test the load from Store, I started with a new
visual.im, loaded Seaside and then loaded my Seaside application package. 19 methods were listed as 'unloadable', all from one class. Store indicated that the class was not defined in the application package; the image it was published from showed showed that it was. Moving the class to another package, then back, and publishing again made no difference. What finally worked was to rename the class and publish again.
I work with two development images, one at the office and one at home, and the application is deployed as a Seaside image on Linux. My normal activity is to publish to Store from one of the development images and then load into the other two. Obviously this class used to load correctly.
I have no idea what happened to cause the problem, but I'm now keeping a test image available to load the package into an image with no history. The only reason we noticed something was wrong was that a method from another class was deleted from the image after the package was loaded, even though Store showed the method correctly defined. That problem I cannot recreate; wish I could, it was even more interesting.
For now we'll watch things carefully, and we'll upgrade to 7.7.1 as soon as the disks arrive.
Bob Nemec
Cherniak Software
_______________________________________________
vwnc mailing list
[hidden email]
http://lists.cs.uiuc.edu/mailman/listinfo/vwnc
Locked
