Elliot, prior to GemFire 7.0, the modules were bundled separately and contained their own copy of the gemfire.jar file. Since 7.0, the modules have been included with the GemFire product bundle and it was thought to be redundant (and to reduce size) to also include the same gemfire.jar in each of the module bundles, thus requiring a user to copy the gemfire.jar into the template's lib directory. If you wanted to source the gemfire jar from elsewhere, you might be able to do so by setting CATALINA_OPTS before starting tcServer.
GemFire HTTP Session Module
Regarding the installation of the GemFire HTTP Session Module for tcServer, why do we need to copy the jar to the ./lib directory? Shouldn't a properly defined classpath replace the need to have the jar files in the ./lib of the tcserver instance? The issue I see here is that if GemFire is upgrade then those copied jar's will also need to be re-copied.
Please sign in to leave a comment.