We have large applications with 13 modules. Based on the requirement of the customer, we should be able to deploy the main module + customer specific module. We are planning to break the app into several wars. Now the problem is that we have some common jesp. Header.jsp, error.jsp etc. Is there any way by which we can keep the original war in normal war and will be able to use the remaining wars or I have to copy it during the attack in the JSP construction process war I know that CSS and Javascript files can be shared in ear packaging in many wars but are not sure about JSP.
Good question. You will be glad to hear that the answer is "yes", although it is very much dependent on how your overlays container is configured.
This JSTL & lt; C: import & gt; tag, which has an optional reference attribute, which is defined as the following:
References to some other local web application to import Resource by name (beginning with a /)
Say that you have deployed WebApp A under the reference route, / a , and WebApp B to / b , Then using a JSP in A, you can use x.jsp B:
It's all very nice and pink, but it has to go through the servlet container's security system, and it can not allow operation. for example,.
Comments
Post a Comment