- This topic has 1 reply, 2 voices, and was last updated 18 years, 1 month ago by
.
-
Posts
-
We got a include.jsp file directly inside our webroot containing taglib declarations such as:
<%@ taglib uri=”http://struts.apache.org/tags-bean” prefix=”bean”%>
<%@ taglib uri=”http://struts.apache.org/tags-html” prefix=”html”%>This file is included by all JSP files with
<%@ include file=”/include.jsp”%>
This normally works fine – autocompletion & validation works. However, when editing a JSP file inside the src folder (such as src/com/foo/bar/example.jsp), it doesn’t work. Does anyone know any workaround or issue with this?
Mike,
It might be a project configuration issue since JSP files are normally place under the web root folder in the path that corresponds to their lookup context from the root URL. Placing them in the src folder will copy them to WEB-INF/classes/com/foo.. at deployment time which is likely not what you want. This alteration could also break content assist and validation, as you found, in addition to making the deployed project unusable in the server.
