Hi Sergio, The reason why this is troublesome is because we need to override some system classes through the boot classpath. This is required to perform certain instrumentations that we can't do any other way at the moment.
Another difficulty is that we need to be able to plug in as early as possible into the class loader hierarchy to be able to properly handle the instrumentation of types that are common between your class loaders / web applications (for instance the Tomcat session handling). We're actively researching possibilities but haven't found the 'holy grail' yet. There are some JVM-level improvements that we have formulated for Sun's JVM team which could eventually make this a possibility, but at the moment we don't think that the JVM itself provides us with the hooks to be able to make this a reality. Hope this clarifies things a bit. Take care, Geert On 16 Feb 2009, at 10:32, Sergio Bossa wrote: > Hi guys, > > I'd like to know what are your thoughts about embedding Terracotta in > your own (clustered) application, in order not to have to "install" it > in a separate location, and more important, not to have to setup the > Terracotta environment through external scripts. > In other words, let's say I have a war application which I want to > cluster with Terracotta: I'd like to bundle the Terracotta > distribution with the war file, without having to download and point > to an external Terracotta location, and then deploy it without having > to setup env variables and run the dso-env script before starting the > application server. > > What do you think? > Are there any plans to support such a feature? -- Geert Bevin Terracotta - http://www.terracotta.org Uwyn "Use what you need" - http://uwyn.com RIFE Java application framework - http://rifers.org Flytecase Band - http://flytecase.be Music and words - http://gbevin.com _______________________________________________ tc-dev mailing list tc-dev@lists.terracotta.org http://lists.terracotta.org/mailman/listinfo/tc-dev
