The header contains 3 tabs representing 3 webmodules. These modules
represent a way how a user can switch from one portion of the application
to another one. The module tabs should be in the order:
Module 1 | Module 2 | Module 3
Module 1 should be active.
The preview contains code snippet that shows you how easy it is to define
your modules either programmatically in your application or in the
configuration files.
Click
here
to display preview.
Click
here
to hide preview.
This code snippet shows you how easy it is to define
your modules programmatically in your application
WebModuleDefinitionManager manager = null;
WebModule module1 = TestWebModule1.getInstance();
WebModule module2 = TestWebModule2.getInstance();
WebModule module3 = TestWebModule3.getInstance();
module1.setURL("core/jsp/layout/applicationmoduletest1.jsp");
module2.setURL("core/jsp/layout/applicationmoduletest2.jsp");
module3.setURL("core/jsp/layout/applicationmoduletest3.jsp");
manager = WebModuleDefinitionManager.getInstance();
manager.add(module1);
manager.add(module2);
manager.add(module3);
request.setAttribute("activemodule", "module1");
This snippet that you how easy it is to define
your modules using standard web.xml configuration file
Here we list of the web client modules that are available in the system
<context-param>
<param-name>oss.webclient.module.0</param-name>
<param-value>org.opensubsystems.security.www.SecurityWebModule</param-value>
</context-param>
<context-param>
<param-name>oss.webclient.module.1</param-name>
<param-value>org.opensubsystems.portal.www.PortalWebModule</param-value>
</context-param>
Here we list of the URL for web client modules that are available in the system.
There have to be also defined particular oss.webclient.module parameter above.
<context-param>
<param-name>oss.webclient.module.url.0</param-name>
<param-value>osssecurity</param-value>
</context-param>
<context-param>
<param-name>oss.webclient.module.url.1</param-name>
<param-value>ossportal</param-value>
</context-param>
end of preview
