If all you are after is storing your sessions in the database, have you considered configuring it in the app server? Both Jetty and Tomcat have solutions.
On Wed, Feb 22, 2012 at 8:07 AM, tompeter <i...@tomkrause.com> wrote: > Hi, > > I am also trying to use an alternate storage strategy but Tapestry doesn't > load mine. > Could you give me a hint on what I did wrong? > > 1. I created my own Strategy in TPGStatePersistencyStrategy.class which > implements ApplicationStatePersistenceStrategy and extends > SessionApplicationStatePersistenceStrategy > 2. I added the following line to my AppModule: > binder.bind( ApplicationStatePersistenceStrategy.class, > TPGStatePersistencyStrategy.class); > > Having placed loggers in the get, set and exist methods, I don't see any > output, neither do I see any errors. > > I very much appreciate your help. > > Thanks and best, > Tom > > -- > View this message in context: > http://tapestry.1045711.n5.nabble.com/Best-practise-to-extend-tapestry-5-so-http-sessions-are-stored-in-db-tp2422175p5505487.html > Sent from the Tapestry - User mailing list archive at Nabble.com. > > --------------------------------------------------------------------- > To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org > For additional commands, e-mail: users-h...@tapestry.apache.org > >
