(rep by Simon Watson)
I'm very new to Hessian and, having got the basic examples working plus reviewed the docs, I have a question - is it possible to pass Java objects via Hessian that implement a common interface, but have different client/server implementations?
I'd like to use it for communication between an Android app and a Spring web application. The Java interfaces for objects passed back and forth are shared, but the server-side implementation of them contains additional JPA stuff which I'd rather not have on the Android client side. Is there any way of (de)serializing objects with a neutral name (rather than fully qualified class name), and define a mapping between this and the different implementations on each side?