--
View this message in context:
http://old.nabble.com/Wicket-1.4.5-%3A-Spring-integration-problem--tp27237445p27435266.html
Sent from the Wicket - User mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsu
quot;>>>"+
> >>> ((NihonBareApplication)getApplication()).getCommonService());
> >>> return
> >>> ((NihonBareApplication)getApplication()).getCommonService();
> >>> }
> >>> }
> >>>
> >>>
>
t; ((NihonBareApplication)getApplication()).getCommonService());
>>> return
>>> ((NihonBareApplication)getApplication()).getCommonService();
>>> }
>>> }
>>>
>>>
>>> But eventhough the bean injected into 'NihonbareApplication' object, the
>>> getCommonService(
Thanks Pierre,
yes,that was a problem with web.xml ,
I forgot to change the filter setting :
applicationFactoryClassName
org.apache.wicket.spring.SpringWebApplicationFactory
Now everything works fine.
Pierre Goupil wrote:
Maybe it comes from the web.xml : can
Maybe it comes from the web.xml : can we ses it, please?
Regards,
Pierre
On Wed, Jan 20, 2010 at 7:41 AM, Ashika Umanga Umagiliya <
auma...@biggjapan.com> wrote:
> Greetings all,
>
> I followed the easy 'Application Object Approach' to integrate Spring with
> my Wicket app. (
> http://cwiki.ap
Greetings all,
I followed the easy 'Application Object Approach' to integrate Spring
with my Wicket app.
(http://cwiki.apache.org/WICKET/spring.html#Spring-ApplicationObjectApproach
)
In my application class :
public class NihonBareApplication extends WebApplication
{
private CommonSe
code will then look like this:
mockery.checking(new Expectations() {
{
oneOf(eventRepository).update(with(any(Event.class)));
}
});
tester.clickLink("content:events:0:d
Instead of using a test stub, i'd use jmock or some similar mock
framework and get a little more control :)
2009/4/6 Olivier Michallat :
> The problem is that your unit tests run out of the web container, you
> can't rely on a servlet context listener to load the Spring context in
> this situation
The problem is that your unit tests run out of the web container, you
can't rely on a servlet context listener to load the Spring context in
this situation.
You need a hook to inject a mock context when testing. This post
describes a solution: http://blog.ehour.nl/index.php/archives/21
2009/4/6
--
>>> -------
>>> Tests run: 2, Failures: 1, Errors: 0,
>>> Skipped: 1, Time elapsed: 0.498 sec <<< FAILURE!
>>> init(domain.TestHomePage) Time elapsed: 0 sec <<< FAILURE!
>>>
Sorry, didn't see (at first) that you've already done something similar.
Anyway, try replacing "classpath:applicationContext.xml" for
"WEB-INF/applicationContext.xml". I'm not sure if this classpath param works
there.
Regards,
Leandro.
2009/4/6 Leandro Féres
> You must tell where's your sprin
You must tell where's your spring context (applicationContext.xml).
Try this:
org.springframework.web.context.ContextLoaderListener
contextConfigLocation
WEB-INF/applicationContext.xml
Regards,
Leandro.
2009/4/6 HHB
> Hey,
> I'm trying to integrate Spring 2.5 into our Wicket
>
Hey,
I'm trying to integrate Spring 2.5 into our Wicket
application, I did the following:
web.xml:
contextConfigLocation
classpath:applicationContext.xml
org.springframework.web.
context.ContextLoaderListener
OpenSessionInViewFilter
13 matches
Mail list logo