Hi!
#629, W2000
I experience a problem with JSPs using static includes, where the editor
thinks it "recognizes" syntax errors, when there actually are none. This is
*not* the "old" static-includes-don't-work problem (because that is now
fixed), but a bit more involved. The editor doesn't seem to be able to
follow the whole "include-path" (or how you call it).
A bit hard to describe, so I'll give an example:
The following JSP code works (of course):
<%@ page import="java.io.*" %>
<%
File f = new File("test");
f.delete();
%>
IDEA doesn't show any problems either.
Now, if the "import" is moved to a statically included page, it nowadays
still works (in #629):
<%@ include file="/includeA.jsp" %>
<%
File f = new File("test");
f.delete();
%>
(where "includeA.jsp" only contains: <%@ page import="java.io.*"%>)
However, if instead the declaration of "f" is moved to an included page, it
doesn't work anymore:
<%@ page import="java.io.*" %>
<%@ include file="/includeB.jsp" %>
<%
f.delete();
%>
(where "includeB.jsp" only contains: <% File f = new File("test"); %>).
IDEA shows "delete" as a syntax error, with the message "Cannot resolve
symbol delete".
This is not correct, because the above construct is legal JSP code and works
without problems.
Johannes
_______________________________________________
Eap-bugs mailing list
[EMAIL PROTECTED]
http://lists.jetbrains.com/mailman/listinfo/eap-bugs
