- This topic has 6 replies, 3 voices, and was last updated 20 years, 4 months ago by
.
-
Posts
-
Eclipse Version: 3.0.0 Build id: 200406251208
MyEclipse Version: 3.7.200 Build id: 200407091200-3.8-Beta2JSK 1.4.2_05 on WinXPprof
although *.jspf files have the MyEclipse JSP editor assigned, there’s no ‘MyEclipse ‘ entry in their context menu, ==> no JSP validation possible.
That’s because you can’t really validate a fragment since it could be included inside dozens of different JSP’s. Within which context would we evaluate it because it doesn’t need to be valid except when included in its final execution context.
Ok, you’re right. But at least some basic validation should be possible (closed tags, Java syntax, etc).
In fact, the whole JSP validation/compilation is so slow, that I believed dependencies were searched for at compilaton… 😳
b0rg,
We have talked in the past of providing full validation for jspf files by actually revalidating/compiling all of the files they are included in… that’s the only way to know, because you can do thing like open a tag in a jspf file, and close it in a jsp file… which by itself makes the jspf totally invalid and useless. this is another reason editing of jspf is so limited, the ‘known context’ of the page is almost nothing.I believed dependencies were searched for at compilaton…
Actually, they are. It’s just that the ‘top-level’ JSPs that include the fragments are fully assembled and then compiled so errors will show up there, in their full context, rather than in the fragments themselves.
Hmmm, I see. This is the vicious circle:
– a.jsp includes b.jsp (not ‘.jspf’, just ‘.jsp’, many projects were born like this…)
– both a.jsp and b.jsp get compiled –> b.jsp signals error because it’s in fact a incomplete ‘jspf’.
Question: could _theoretically_ a option “don’t compile *.jsp which are included in other files” be implemented or ME doesn’t even notice this detail (probably it’s JSP compiler’s task) ?
