I think a crude example of what you're after is here: https://svn.terracotta.org/repo/forge/projects/terracotta-toolkit-framewor k-sample/trunk
I haven't studied it too much, but I think it is meant to show how one can instrument your own types along with the toolkit. It is worth noting that we haven't spent any effort on trying to make this use case easy or friendly. Toolkit usage is geared towards serializable objects for the happy path. I'm not sure I quite get what you're asking for in the second question. The instrumentation we do to classes to make them "clusterable" isn't geared towards providing the change events to anything other than terracotta runtime. There isn't a way to just add in arbitrary listeners. That kind of pattern is available (albeit at a much higher level) in ehcache. -tim > -----Original Message----- > From: tc-dev-boun...@lists.terracotta.org [mailto:tc-dev- > boun...@lists.terracotta.org] On Behalf Of Pavel Chlupácek > Sent: Friday, August 13, 2010 2:04 AM > To: tc-dev@lists.terracotta.org > Subject: [tc-dev] Insrumentation with tim-toolkit > > Hi, > > can anybody please help me/point me to place where instrumentation > example for custom classes for TC toolkit (express mode) is documented? > I saw a posts about the ways how to do it in "dev-freindly" way, but I > would be keen to have anything which just work atm. > > Also is there a possibility if class gets instrumented to hook to code > which updates class on cluster change (I mean local instance of class) > to eventually run custom serialization invalidation locally? > > Thanks a lot > Pavel. > > > _______________________________________________ > tc-dev mailing list > tc-dev@lists.terracotta.org > http://lists.terracotta.org/mailman/listinfo/tc-dev _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
