Igor Vaynberg wrote:
On Tue, Nov 10, 2009 at 3:55 AM, Kenny MacLeod <kenny.macl...@kizoom.com> wrote:
Hi there,
2) A modified AnnotProxyFieldValueFactory which gives the option of not
creating CGLIB proxies for the injected Spring beans. In deployment
environments where session serialization is not enabled, it seems an
unnecessary restriction to require that these proxies be created, given that
not all target beans can be proxied in this way. By allowing this
restriction to be relaxed, a wider set of scenarious can be catered for. The
new flag is passed in from a modified SpringComponentInjector.
this is highly dangerous. while this may work for a quick
dev-give-it-a-try test it will fail in most production environments.
wicket is not the only thing that serializes pages. the servlet spec
says that anything you put into a session *must* be serializable.
a) containers will sometimes swap inactive sessions to disk in order
to free up some memory - they do this via serialization.
b) container serialize sessions when clustering.
I agree that it should be no means be the default setting, but in some
cases you *know* your production environment does not serialize sessions.
For example, we run in a JBoss cluster with Tomcat session replication
disabled. Our sessions are full of legacy objects that are not
serializable, and it causes no problem whatsoever. There's no
replication, and no session passivation.
All I'm suggesting is that the option is made available, with suitable
health warnings.
kenny
