/
/bean
-Original Message-
From: Loritsch, Berin C. [mailto:berin.lorit...@gd-ais.com]
Sent: Tuesday, November 17, 2009 4:15 PM
To: users@wicket.apache.org
Subject: RE: Spring/Wicket/Hibernate testing driving me banana nuts
I've got the part that injects a Spring WebApplicationContext
i see you are using MockWebApplication in your tests. this application
does not install the SpringComponentInjector and so @SpringBean has no
effect.
you should either give wickettester an instance of your actual
application class, or create a mock one that installs
springcomponentinjector.
on its own to
use?
-Original Message-
From: Igor Vaynberg [mailto:igor.vaynb...@gmail.com]
Sent: Tuesday, November 17, 2009 4:05 PM
To: users@wicket.apache.org
Subject: Re: Spring/Wicket/Hibernate testing driving me banana nuts
i see you are using MockWebApplication in your tests
, November 17, 2009 4:05 PM
To: users@wicket.apache.org
Subject: Re: Spring/Wicket/Hibernate testing driving me banana nuts
i see you are using MockWebApplication in your tests. this application
does not install the SpringComponentInjector and so @SpringBean has no
effect.
you should either
:15 PM
To: users@wicket.apache.org
Subject: RE: Spring/Wicket/Hibernate testing driving me banana nuts
I've got the part that injects a Spring WebApplicationContext into the
WicketTester already (Source attached). I should be using the application
class, if I'm not then something has changed
C. [mailto:berin.lorit...@gd-ais.com]
Sent: Tuesday, November 17, 2009 4:15 PM
To: users@wicket.apache.org
Subject: RE: Spring/Wicket/Hibernate testing driving me banana nuts
I've got the part that injects a Spring WebApplicationContext into the
WicketTester already (Source attached). I
