|Best Practice for extending the in-built Tomcat bundle [message #659655]
||Mon, 14 March 2011 22:28
| Matt Fellows
Registered: February 2011
I'm wanting to use Terracotta with Virgo for replicating Web Sessions  and distributed caching with EHCache.
Basically, you install a Value in a Tomcat <Context> configuration element and it pipes the session data into Terracotta to manage, which requires the Terracotta JARs to be on the classpath for Tomcat and Terracotta requires access to the Tomcat libs (i.e. org.apache.catalina.*)
To achieve this I understand there are a few options:
1. Create bundle's out of the Terracotta libraries, install into Equinox and modify the Tomcat bundle to import those libraries
2. Create bundle's out of the Terracotta libraries, install into Equinox and create a bundle fragment
3. Adding the libs to one of the booting classpaths of the entire system (seems like a worst case scenario).
4. + 5. The same as the first 2, but embed the libraries directly into the bundles/fragments.
I was wondering if there is a best practice\recommendation around modifying base functionality? The fragment seems like the most elegant approach, but I'm not sure if it will work how I expect.
Any advice would be much appreciated.
1. http://www.terracotta.org/documentation/web-sessions-install .html#50499643_92283
Powered by FUDForum
. Page generated in 0.02497 seconds