Closed caim2015 closed 4 years ago
When I change 'relative' path to 'absolute' path like the following,it becomes work. The precompilation error is successfully ignored.
<%@ include file="./b/button.jsp"%> ↓ <%@ include file="/page/b/button.jsp"%>
As we all know,in the JSP Include directive using 'relative' and 'absolute' path both are valid. So,I think this is a bug .
The JSP specification recommends the .jsp
extension be used only for files corresponding to top level JSP files, forming a complete JSP page when processed. What happens if you use .jspf
for the fragment file name and change nothing else?
The JSP specification recommends the
.jsp
extension be used only for files corresponding to top level JSP files, forming a complete JSP page when processed. What happens if you use.jspf
for the fragment file name and change nothing else?
If .jsp
is changed to .jspf
, the error do not happen.
Because even if [Precompile JSPs] is selected, the "button.jspf" is not be precompiled.
Only the .jsp
, .jspx
files are precompile targets.
button.jsp ↓ button.jspf <%@ include file="./b/button.jsp"%> ↓ <%@ include file="./b/button.jspf"%>
This issue has been marked as inactive and old and will be closed in 7 days if there is no further activity. If you want the issue to remain open please add a comment
Environment Details
JDK version:JDK8
Problem Description
My test sample is very simple. Only two JSPs. 1.moto.jsp
2.button.jsp
When I deploy my sample,[Precompile JSPs]is selected from Web Console, I get this error:
In order to ignore this error, I set "ignoreJspFragmentErrors" to true. but it does not work.
sample_NO.zip