Rice currently defaults to java serialization for remoting... instead of SOAP. This is primarily due to performance reason.
One issue with using serialization is that switching JVM's could cause differences in the way objects are serialized. ex. Java 5 client connecting to java 6 server.
We need to run some speed tests to see which is faster, soap or searial for remoted services.
For this particular case we upgrading the recipe sample app to spring 1.0.3 (snapshot) and tested that against the standalone server.
We created a simple servlet inside the sample app. All this servlet does is take in a request param to switch the underlying service call to use serialization or soap remoting.
Our test calls the identityService.lookupEntityInfo with an empty map. This will return a relatively large payload.
Soap vs Java Serialization
Oracle vs MySql
Soap Security On/off