Is the issue of naming a classloader to make integrations work still an issue in TC 2.6?
DOC-285 asks for a note to inserted into the docs about this issue, but I'm not sure I understand it. Does the following have to be executed when loading the clustered app: -Dcom.tc.loader.system.name=<name_of_classloader> Does <name_of_classloader> have to be specified in tc-config.xml? Does this affect every framework and container that TC integrates with? --------------------------------------------------- Igal D. Levy Terracotta Inc. terracotta.org | terracottatech.com 415-738-4026 _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
