Hi,
essentially you need the same classes on both sides of the communication.
If you have a classe
Spaceship under the namespace
my.game from client side you will need an equivalent class with the same name and package name on the server side.
In this case it looks like the server side is not able to find the class that maps to the object sent from the client side.
The RpgModel.jar from the example is the jar file containing all classes that map the objects you're sending from client side.
When the server receives a serialized version of the
SpaceShip class from the client it will look for the same class in the global classpath. If the class can't be found it will throw an Exception such as the one you've reported.
Since Extensions are loaded in the their custom class loader, the server will not be able to find those classes. Hence the need to deploy them separately at the top level of the classpath.
If you're not entirely familiar with the classloading mechanism in Java you should read this:
http://docs2x.smartfoxserver.com/Extens ... d-conceptsIf you prefer to avoid class loading issues altogether simply deploy all your Extension classes under
extensions/_lib_/ Hope it helps
