this type of pattern with
Spring in other settings and thought it might be useful in Wicket too.
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Wed 3/19/2008 5:49 PM
To: users@wicket.apache.org
Subject: Re: Suggested Enhancement To Spring Support
you want
and thought it might be useful in Wicket too.
From: Igor Vaynberg [mailto:[EMAIL PROTECTED]
Sent: Wed 3/19/2008 5:49 PM
To: users@wicket.apache.org
Subject: Re: Suggested Enhancement To Spring Support
you want to swallow the exception?
then you would
Thanks for the explanation, that makes perfect sense.
From: lars vonk [mailto:[EMAIL PROTECTED]
Sent: Thu 3/20/2008 10:16 AM
To: users@wicket.apache.org
Subject: Re: Suggested Enhancement To Spring Support
Spring support in Wicket works with proxies, so your
It might be a nice improvement to Wicket's Spring support to allow for
missing bean definitions to be handled gracefully. This would allow for
the use of a sane default in the absence of explicit declaration in the
context XML. Right now using the Spring annotations support I get the
following
you want to swallow the exception?
then you would return a null into a proxy and cause an npe later...
-igor
On Wed, Mar 19, 2008 at 1:43 PM, Zappaterrini, Larry
[EMAIL PROTECTED] wrote:
It might be a nice improvement to Wicket's Spring support to allow for
missing bean definitions to be
