Not all conflicts listed at the beginning of this section can be completely overcome. Below is a summary of the remaining restrictions and incompatibilities.
This may seem a bit much to ask, since in a typical client-server environment only the service objects are exported and they become garbage only when the service is shut down. However, this approach is technically correct in that no non-garbage object will ever be incorrectly collected. Note that because SST adheres to RMI's notion of client behavior with respect to DGC, objects exported by a Java server will be correctly garbage collected.
When mapping objects between Java and Smalltalk, you are typically mapping instances. However, it is possible to map a Smalltalk class to an instance of a Java object. SST provides an example of this technique in the SstPingPongRmi example. Notice that the sstRmiClassName method appears on both the class and instance side of SstPingPongRmi example.