-
Notifications
You must be signed in to change notification settings - Fork 1.7k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Make proxies serializable #12
Comments
From crazyboblee on February 14, 2007 11:13:17 (No comment was entered for this change.) Labels: -Type-Defect Type-Enhancement |
From limpbizkit on May 30, 2008 09:22:52 I think I have a possible strategy for the fix, but its tricky. Suppose the intercepted class looks like this: Then the Guice generated AOP class looks approximately like this. This is my speculation, I'm not actually The problem is that it's very unlikely that the other end is going to have a class like Foo$EnhancedByGuice. Of course, the removeSuperclass() and asSubclass() methods need to do something quite magical. They need One requirement is that we must use the user's provided Foo.writeReplace() and Foo.readResolve() methods. One way to get around Unsafe would be to get Java's serialization to do the unsafe stuff for us. Perhaps a |
From limpbizkit on June 03, 2008 02:39:24 I talked to Bob about this. We're not going to implement this since it has dangerous consequences, especially if it * - serializing interceptors is dangerous (they require heavyweight configuration, like transaction managers,
Status: WontFix |
From limpbizkit on June 03, 2008 17:29:53 Turns out it isn't too difficult to implement removeSuperclass() and asSubclass() using reflection and |
From crazyboblee on February 14, 2007 14:13:01
So you can store proxies on the HTTP session, etc.
Original issue: http://code.google.com/p/google-guice/issues/detail?id=12
The text was updated successfully, but these errors were encountered: