There is an ancient issue that requesting pretty much the same thing, though more focused on locks, etc. See https://jira.terracotta.org/jira/browse/DEV-178
regards, Eugene Geert Bevin wrote: > Hi, > > just sending this to tc-dev to gather some comments on the root of > this issue's problem: https://jira.terracotta.org/jira/browse/DEV-899 > > I personally think that this a fundamental aspect of Terracotta that > needs to be discussed. What happens here is that a shared root is > being made 'static' across web applications when the classes of the > roots are present in separate jar files in different web > applications. This is the wrong behavior imho. I think that this even > goes back further, is it ok to assume in a container-based > application that all clustering is setup in a container-wide tc- > config file that has a single scope? This works for standalone > applications, but when there are several applications running in the > same container, shouldn't it be possible to have sub-tc-config files > that, like web applications, have separated scopes? > > Any thoughts? > > Geert _______________________________________________ tc-dev mailing list [email protected] http://lists.terracotta.org/mailman/listinfo/tc-dev
