Jeremy Thomerson wrote:
File a JIRA and attach the patch. At least that way they won't get lost.
https://issues.apache.org/jira/browse/WICKET-2572
https://issues.apache.org/jira/browse/WICKET-2573
kenny
James Carman wrote:
On Tue, Nov 10, 2009 at 12:00 PM, Kenny MacLeod
wrote:
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
Igor Vaynberg wrote:
On Tue, Nov 10, 2009 at 3:55 AM, Kenny MacLeod 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
Hi there,
I've been looking at the wicket-spring integration stuff, and I've come
up with a couple of enhancements which I've found useful, and would be
happy to contribute:
1) An enhanced SpringWebApplicationFactory which has the capability of
creating and initializing its own Spring appco
