I believe a major difficulty in achieving a small app server footprint is the need to provide different versions of jar files used by the web apps that have been deployed. Jar versions lead to duplication since each web app is likely to provide copies of the versions of jars it needs inside its own war file. As I currently see things, a significant advantage of OSGi is that it can provide jar (i.e. bundle) versions with minimal duplication, thereby reducing the server footprint. Is there another way to reduce jar duplication when using tc Server, so that OSGi is not needed? If not, are there instructions for OSGi-ifying tc Server so that it could be used e.g. instead of Tomcat in an Apache Virgo server? I would very much appreciate some guidance. Thank you.
Login or Sign Up
- Log in with