On Tue, 03 Mar 2009, Chris Hansen wrote: > The situation that I'm dealing with most commonly is where I'm dealing > with simple, DTO-like POJOS with no-arg constructors and > getters/setters (why they are not serializable in the first place is > beyond me). It just seems like it would be possible, in this simple > case, to create a proxy for each object in the object graph which is > not serializable until you get down to the actual data (i.e. > primitives, Strings, etc.) which is serializable. The proxies would > have to keep track of whatever information they need to de-serialize > themselves (e.g. class name and constructor). It seems like this has > not been implemented, but do you think it is possible to do so?
That sounds cumbersome too :) If the objects are in fact serializable, why can't you make them Serializable? Alternatively, you could create Serializable wrappers for them. Doing that to DTOs sounds strange though :) Some people use HttpSessionStore and don't replicate nor persist their sessions, but I suppose that's not a supported nor advisable approach. Best wishes, Timo --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
