[opencms-dev] Shipping the libraries as part of the module

Ramon Gavira Sáenz ramon.gavira at sagasoluciones.com
Mon Jun 7 17:18:35 CEST 2021


Hello,

In OpenCms Doc Central, when talk about modules (Modules (opencms.org)<https://documentation.opencms.org/opencms-documentation/the-opencms-workplace/launchpad-and-other-apps/modules/>)

There is a parr where it says this:

Create lib subfolder
If checked, the folder /system/modules/{module package name}/lib is created automatically. In this folder Java libraries shipped with the module are typically placed. The folder is then configured as export point to the webapp's lib folder on the RFS. Hence, after module installation and restart of the servlet container the library is automatically present.

Be careful shipping the libraries as part of the module and using the export point mechanism. In particular when replacing or deleting a module, your servlet container may crash, since - depending on the servlet containers configuration - it will miss the exported jar that is removed in module deletion. You might simply deploy your libraries separately to prevent such issues.


at that point it warns of possible problems when deleting or updating modules. the text says this depends on the configuration of the servlet container. We are using Tomcat 8, Anybody knows how to configure it to bypass that situation a not need to deploy libraries separately?

Thanks for helping!


Ramón.


Ramón Gavira Sáenz

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <https://lists.opencms.org/pipermail/opencms-dev/attachments/20210607/df1f1b35/attachment.htm>


More information about the opencms-dev mailing list