Re: Injecting proxy services in page.

2013-06-18 Thread martin.dilger
To be honest, I dont understand exactly what the Problem is. If you work with Spring-Beans, they are normally safe to serialize, as its only the proxy. We┬┤ve done this all the time (even with older wicket versions) without any problems. It looks like you have some Classpath-Issue here. The

Re: Injecting proxy services in page.

2013-06-17 Thread eugenebalt
We've heard that there is a fix for this available in Wicket 1.5. However, we are stuck with Wicket 1.4.7 and cannot upgrade, for various reasons. (We're also already using the AnnotationConfigWebApplicationContext referred to in the previous post.) Are there any other workarounds for this

Re: Injecting proxy services in page.

2013-06-06 Thread harmoniaa
If you are already using XmlWebApplicationContext (extends AbstractRefreshableWebApplicationContext like AnnotationConfigWebApplicationContext) that is probably not the issue, but you can set the context class in your web.xml like this: servlet ... init-param

Re: Injecting proxy services in page.

2013-06-05 Thread Entropy
At the risk of turning this into a Spring discussion on a Wicket forum, how does one control that? I would like to try your suggestion, but am not sure what knob to twist. We just implement ApplicationContextAware, and point to our spring config file in web.xml. I don't set anywhere asking for

Re: Injecting proxy services in page.

2013-06-03 Thread Bertrand Guay-Paquet
Hi, I don't use Spring, so I can't help you specifically. However, there is a chapter about integration with Spring in the free wicket guide here: https://code.google.com/p/wicket-guide/ (chapter 17.2) On 03/06/2013 9:00 AM, Entropy wrote: We are doing the annotation based approach described

RE: Injecting proxy services in page.

2013-06-03 Thread Paul Bors
I find it easier to configure Spring via the XML rather than code. Hence I have my applicationContext.xml inside my war's WEB-INF/classes/ with all the bean definitions and then configure Wicket via the context specific configuration from inside my web.xml: !-- There are three means

Re: Injecting proxy services in page.

2013-06-03 Thread Edvard Fonsell
Hi, I'm not sure if this is the issue here but I've seen similar problems when I used AnnotationConfigApplicationContext as a Spring context, but got it working by using AnnotationConfig*Web*ApplicationContext. br, Edvard On 03.06.2013 17:19, Paul Bors wrote: I find it easier to configure