I've started piddling about with doing a small skeleton app for
springframework/webwork 1.4 integration. The bean wiring stuff works
quite nicely, so I thought I'd go a little crazy and try to get
interceptors (via the aopalliance stuff in Spring) working, so us poor
1.4 users can finally stop
Just for my own understanding, is this a problem only for just the spring
framework dynamic proxies, or does the value stack implementation have
issues with dynamic proxies in general? Where does the value stack get
confused? Is it in XWork code or in OGNL code?
On Wed, 31 Dec 2003 02:48:43
This is for webwork 1, so no xwork or OGNL (although I suspect OGNL
would have the same problem).
The object that you get back from an intercepted call is of type
__$proxy1, so OGNL/webwork checks property descriptors for that class,
rather than the underlying actual class.
On Dec 31, 2003,
