Re: [Wicket-user] WicketTester replaces Application class

[Ingram Chen]

yea... That's one of major drawback of WicketTester since it heavily relies on MockWebApplication. so I personnally avoid to use Application to manage resources.

To test with Spring, wiki has an excellent integration and testing, see:

   http://www.wicket-wiki.org.uk/wiki/index.php/Spring

You may got some ideas there.

On 3/14/06, Nick Heudecker <[EMAIL PROTECTED]> wrote:

The problem with WicketTester is it replaces your Application subclass, so if you're using something like Spring, you no longer have access to Spring-managed beans.  Is there a convenient workaround for this?

--
Ingram Chen
Java [EMAIL PROTECTED]
Institue of BioMedical Sciences Academia Sinica Taiwan
blog: http://www.javaworld.com.tw/roller/page/ingramchen