Classloader naming is still definitely something that must be considered with regards to TC integration, although it isn't really a concept I think is relevant to "everyday" terracotta usage. It's more relevant to those who are creating new TC integrations with frameworks and containers, not the users of those frameworks/containers. The concepts around classloader naming aren't well documented (if at all), but it has been discussed on tc-dev before. This is the last of at least one thread about it: http://www.mail-archive.com/[email protected]/msg00233.html
Dealing with classloader naming is definitely a consideration supporting new web containers. It isn't usually something that needs attention for most libraries/frameworks, but there are exceptions to that rule (RIFE comes to mind) DOC-285 doesn't really have anything to do with named classloaders. It's talking about an API that TIM writers can use to artificially export/inject classes into existing classloaders. It's a whole other topic :-). As is the is business with that " Dcom.tc.loader.system.name" system property. Unfortunately I don't think DOC-xxx JIRA items are public, so apologizes to anyone who can't actually see the details here. > -----Original Message----- > From: [EMAIL PROTECTED] [mailto:tc-dev- > [EMAIL PROTECTED] On Behalf Of Igal Levy > Sent: Tuesday, May 20, 2008 3:48 PM > To: tc-dev > Subject: [tc-dev] classloader issue and integrations > > 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 _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
