Yes, This is a slightly unpleasant issue which affects all our proxy instances going back to 0.1 and before. The problem we have is that we can't unwrap the proxy on its way into the ObjectOutputStream (there's nothing we can hook into). As a result you end up with something that either breaks immediately, or is just plain wrong when it gets deserialized.
The only thought I've managed so far is to put in a defaultWriteObject that throws an exception for all our proxys. That doesn't really solve the issue though. If anyone has any bright ideas I would love to hear them! Tim > Date: Sun, 3 Jul 2011 14:17:32 +0200 > From: [email protected] > To: [email protected] > Subject: Proxy Serialization > > Aries Blueprint proxies are not serializable. The problem is, you'd > expect them to be when the proxied class or interface is serializable. > > After all, the proxy should be transparent to the client, and if the > proxied class declares itself to be serializable, then a > non-serializable proxy breaks the API contract of its target. > > I ran into this problem when using Wicket with Aries - Wicket pages and > components get serialized all the time... > > Regards, > Harald > >
