tc-config is almost the same, except need to add <include> <class-expression>org.apache.wicket.protocol.http.pagestore.AbstractPageStore$SerializedPage</class-expression> </include>
or need to make this page implement IClusterable with bytecode stuff, but if you do use bytecode, this needs to happen before it starts looking for instrumented classes (IClusterable is an interface used in wicket to say that the class should be instrumented, is is an extension of the Serializable interface). The wicket tim needs to remove the current code which forces the httpsessionstore, but apart from that i dont think it needs to do anything else. Maybe other people will have ideas? Ari Zilka wrote: > > 1. Can I get the tc-config.xml that goes with this > > 2. Terracotta TIMs can do almost anything we need to do here. We can > replace a method on class load. We can probably pain $SerializedPage > inner class to implement the IClusterable interface as well. I dunno > about removing Serializable though. Would we have to? > > Anyways, if you ship me a list of what your ideal TIM would do I will > get it configured, bundled in OSGi and back to you by Monday. > > I agree though. The TIM could live at Terracotta's forge but should > live with Wicket as it needs to be maintained with changes in Wicket > moreso than changes in Terracotta. > > --Ari > > -- View this message in context: http://www.nabble.com/Terracotta-integration-tp18168616p18380445.html Sent from the Wicket - Dev mailing list archive at Nabble.com.
