Announcement Announcement Module
Collapse
No announcement yet.
one big webmodule for different sub type of web-modules?? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • one big webmodule for different sub type of web-modules??

    Hello All just wondering, in case if application is splitted by domain (i.e., by use case or vertically). Say we have two web modules for user administration and other is order management(but both modules are a part of same par that might be using other modules). So how we can have a one single web modules that uses other two web modules for user mgmt and order mgmt.

    Thanks

  • #2
    one big webmodule for different sub type of web-modules??

    Hi Puran,

    You can't have a web module which is comprised of other web modules; however, you can package multiple web modules within a single PAR, and each web module will be deployed to the Servlet container as a separate web application with its own unique context path. Thus, if the web modules in your application are independent, this would be your best deployment option.

    However, if the proposed "web modules" are interdependent or share common web infrastructure (e.g., Spring Security or Spring Web Flow configuration and beans), you will need to merge them into a single web module. In such a situation, you can still reference types from other bundles in your application (e.g., within a PAR).

    In summary, for all use cases, each web module will be deployed as a single web application in the Servlet container, and the MODULE-INF directory within the web module's bundle serves as the root of the ServletContext. Thus any static resources (e.g., images, CSS, HTML, JSPs, etc.) for the resulting web application must be present in the MODULE-INF directory; whereas, types and services can be consumed from other bundles via standard OSGi semantics.

    Hope this helps,

    Sam

    Comment


    • #3
      one big webmodule for different sub type of web-modules??

      Thanks Sam.
      you made things easier to understand. So basically what it means is that we cannot modularize the UI modules in a web application based on use cases so that it can be deployed in runtime if they are interdependent.

      Comment

      Working...
      X