Proxy for Created GemStone Class Not Removed on Abort
If you start a GemBuilder session, pick a Smalltalk class in a Smalltalk
class browser, and replicate the class in GemStone with
"Create in GS" or "Compile in GS", this will cache a proxy for the GemStone
class just created in GemBuilder. If you then abort the session, the proxy
remains in the GemBuilder cache, even though the class in GemStone no longer
exists, with the result that if you attempt to compile the class in the
new transaction, you will get confirmers asking if you want to overwrite
the old methods, even though the class does not exist in GemStone.
The existence of the proxy can result in the class never getting recreated
in GemStone in the new transaction; "Create in GS" reports no error, but
the GemStone browser and launcher report no such class exists.