[ https://jira.terracotta.org/jira//browse/CDV-371?page=comments#action_22420 ] Eugene Kuleshov commented on CDV-371: -------------------------------------
We do have support for including subclasses or implementations of given interface (using Foo+ expression) as well as including classes with given annotation (@Clustered Foo). Our expression matcher that could potentially match on the superclasses (something like Foo#), but it need to be enabled... > detect all classes that should be instrumented > ---------------------------------------------- > > Key: CDV-371 > URL: https://jira.terracotta.org/jira//browse/CDV-371 > Project: Community Development > Issue Type: New Feature > Components: System Administration > Affects Versions: 2.4-stable1 > Reporter: Erez Harari > Assigned To: Issue Review Board > > I would like to know which classes should be instrumented so i can remove the > ** include. > however, the admin console only lists the leaf level classes, while at > runtime terracotta demands to have all parents as well defined in includes. > so, if the admin console had listed all the classes needed at runtime, it > would be much easier and faster to configure and fewer people would be using > ** and suffer the additional overhead.. > another option is a syntax or an attribute in <include> to include the class > and all its parents. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.terracotta.org/jira//secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
