I've been reading some documentation and making some tests, and it seems to me that there's no sense to use TreeCacheAOP in a web application, to store objects that are loaded by the web application's class loader (or, anyway, classes which come in jars bundled with the application - I guess they are loaded then by the web application's class loader, right?).
What I'm trying to do, is have an object accessible from two web applications. Everything works fine only when the classes are serializable and wrapped in a MarshalledValue instance. In other cases I get a ClassCaseException (as, logically, I should, and as it is written in the FAQ).
So am I missing something important or is really TreeCacheAOP not useable here?
You are correct. Actually, this is an issue for TreeCache as well to deal with scoped class loader.
I am trying to add support for marshalling in 1.2.4 starting from TreeCache layer.
Release 1.2.4 is slated for end of August now.