Then we could use a longer trace from the serialization exception... Plus some code to go with it. The best way would be to create a minimal setup using a quickstart exhibiting the problem.
Martijn On Tue, Jun 1, 2010 at 12:47 PM, Joseph Pachod <[email protected]> wrote: > Martijn Dashorst wrote: >> >> You need to use the Wicket injector for guice. That will create a >> serializable proxy for the service. Guice itself doesn't know about >> Wicket, so you can't expect it to magically work. >> >> Martijn > > sorry, I didn't provide enough context: I'm using wicket-guice (on 1.4.9). > So injection is dealed with by wicket. > > best regards > joseph > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > > -- Become a Wicket expert, learn from the best: http://wicketinaction.com Apache Wicket 1.4 increases type safety for web applications Get it now: http://www.apache.org/dyn/closer.cgi/wicket/1.4.8 --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
