Terracotta added (or re-added?) a feature that lets you define classes to be instrumented including all their sub types. This makes configuring Wicket applications with Terracotta a lot easier, especially now that we introduced a tagging interface IClusterable for this purpose.
Many thanks to Eugene Kuleshov, who implemented this feature and tested it with Wicket. After some last fixes from Matej, nearly all wicket-examples run without problems.
[update]
This post was getting out of date, particularly the configuration bit, which is now much easier. In order not to confuse people, I thought it would be better to remove it.
We should make a terracotta configuration module out of this soon.
Yeah, baby! Terracotta!
I just noticed that the above config file seems to have errors in the pattern expressions. Some packages are “package.*” and some are “package..*”.
package.* includes all classes from a package, and package..* includes all from a package including sub packages.
Terractta uses AspectWerkz’ join point language as defined here: http://aspectwerkz.codehaus.org/definition_issues.html#Join_point_selection_pattern_language. Though reading that it seems that package.. should suffice.