Afaik you can't configure terracotta to serialise objects (its kind of the
opposite of what it tries to achieve), however
simply serialising the webpages doesnt work in all cases anyway (thats what
my original solution did), for example when you have a reference to one
page inside another you can end up with the wrong version of that referenced
page.
The TerracottaPageStore I am working on will take care of this, and when it
is ready the only change you will need to make is adding something like this
in your application class:
public ISessionStore newSessionStore() {
return new SecondLevelCacheSessionStore(this, new TerracottaPageStore(5,
5));
}
it is also posible that this could be added automatically with byte-code
manipulation.
John Patterson wrote:
>
> It seems a shame that this workaround is required to get terracotta to be
> able to handle the amount of garbage created. Would be great if TC could
> be configured to serialise WebPage's and their Components as single
> entities. Is anything like this in the roadmap?
>
> JD
>
>
--
View this message in context:
http://www.nabble.com/Terracotta-integration-tp18168616p18276781.html
Sent from the Wicket - Dev mailing list archive at Nabble.com.
