Home/ Questions/Q 1111791
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-17T02:36:15+00:00

We have a big application having 13 modules. Depending on the customer requirement, we

  • 0

We have a big application having 13 modules. Depending on the customer requirement, we should able to deploy core module+customer specific modules. We are planning to break the app into multiple wars. Now problem is we have some common jsp’s like header.jsp, error.jsp etc. Is there any way by which we can keep the common jsp’s in core war and rest of the wars will be able to use it or I have to copy these jsp’s in the invidiual wars in build process. I know CSS and Javascript files can be shared across multiple wars in ear packaging but not sure about jsp’s.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    Good question. You’ll be happy to hear that the answer is “yes”, although it’s highly dependent on how your servlet container is configured.

    It’s done using the JSTL <c:import> tag, which has an optional context attribute which is defined as:

    Name of the context
    (beginning with a /) of some
    other local web application to
    import the resource from.

    So say you have webapp A deployed under context root /A, and webapp B deployed under /B, then a JSP in A can include x.jsp from B using:

    <c:import context="/B" url="x.jsp"/>

    This is all very nice and rosy, but this has to pass through the servlet container’s security mechanism, and it may not permit the operation. For example, in Tomcat the crossContext attribute must be set to true.

    • 0