JavaServer Page

During the course of module installation, OpenCms checks that all of the new module’s dependencies are already installed. If they are not, OpenCms will not allow the new module to be installed. The Module dependencies screen provides information on the module’s dependencies. These dependencies are listed in the Module dependencies table. If you create a module that uses resources from another module, you have create a dependency. But OpenCms does not automatically detect this. You will need to use the New module dependency button on the Module dependencies screen to add information about this dependency. When the module is exported, dependency information is exported with it. The Export Module Screen Clicking on the Export Module button on the first Edit Module screen will promptly export the module to the file system. Each time you export the module, the module minor reversion number will be incremented by one. That means that when we export the 0.5 version of the St. Nicholas Template module, it will become version 0.6. You can manually edit this field from the Edit Module (tool) button on the Edit Module screen. The new module will be written to the server’s file system, in the directory $CATALINA_HOME/webapps/opencms/WEB-INF/packages/modules. Deleting a Module The seventh and last button on the first Edit Module screen is called the Delete Module button. Clicking on this button will immediately remove the module from OpenCms. Creating a Module Modules can provide a very convenient way of packaging your resources. In particular, templates, jsp files, and java code ought to be stored in modules. As we begin working with templates, we will use a particular module for storing the new template files. We will create this module now. Clicking the first button on the Module Management screen loads the New Module screen.

Note: If you are looking for good and high quality web space to host and run your application check Lunarwebhost Low Cost Web Hosting services