you should inject your dao using one of the provided wicket-ioc modules such as spring or guice. this will create a proxy that is serializable instead of requiring the actual object you are injecting to be serializable.
-igor On Thu, Jun 16, 2011 at 11:00 AM, Brian Lavender <br...@brie.com> wrote: > It seems that I have to extend the serializable interface for > my DAO in order not to get errors. Should I be putting it > in the WebSession area, or elsewhere? > > I have the full context of the sample at the following. It is > a simple Maven project. > http://brie.com/brian/wicket/zebra00.zip > > > public interface CheeseDAO extends java.io.Serializable { > public Cheese getCheese(Long id); > public List<Cheese> getCheeses(); > } > > public class CheesrSession extends WebSession { > private CheeseDAO myDAO = new CheeseDAOImpl(); > > public CheeseDAO getDAO() { > return myDAO; > } > > } > > > Thanks, > > brian > -- > Brian Lavender > http://www.brie.com/brian/ > > "There are two ways of constructing a software design. One way is to > make it so simple that there are obviously no deficiencies. And the other > way is to make it so complicated that there are no obvious deficiencies." > > Professor C. A. R. Hoare > The 1980 Turing award lecture > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org > For additional commands, e-mail: users-h...@wicket.apache.org > > --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org For additional commands, e-mail: users-h...@wicket.apache.org
