- This topic has 1 reply, 2 voices, and was last updated 19 years, 11 months ago by
.
-
Posts
-
I’m just starting with myEclipse 3.8.4 and am encountering some weird behaviour in the JSP editor.
A red squiggly underlines errors in my java code. But when I let my mouse hover above the red squiggly the no usefull error message appears. What does appear is documentation for the method or type. No error marker appears in the left hand gutter. But if I hover where the error marker in the left hand gutter should be, then an error message describing the problem does appear!
I also had a newbie problem because I had given my JSP the same name as my java class, which caused the jsp editor to give spurious error messages. In other words I had both MyClass.java and MyClass.jsp. That one took me quite a while to figure out because the resulting jsp runs perfectly but it causes MyEclipse’s jsp editor to give strange error messages.
A red squiggly underlines errors in my java code. But when I let my mouse hover above the red squiggly the no usefull error message appears. What does appear is documentation for the method or type. No error marker appears in the left hand gutter. But if I hover where the error marker in the left hand gutter should be, then an error message describing the problem does appear!
This is correct behavior (I know strange, but correct.. the invisible marker thing will be fixed soon).
LEFT margin errors are validation errors, they will show up if you try and save/compile the page. RIGHT margin errors are reconciler errors, they are real-time errors that make the squigly lines.
I also had a newbie problem because I had given my JSP the same name as my java class, which caused the jsp editor to give spurious error messages. In other words I had both MyClass.java and MyClass.jsp. That one took me quite a while to figure out because the resulting jsp runs perfectly but it causes MyEclipse’s jsp editor to give strange error messages.
Ahh yes this is a known problem, the editor does not like it when the two classes have the same name because it doesn’t compile the JSPs to their unique name/location like most app servers do, so the compiled class actually conflicts with your Java class. For the time being try to avoid namings like this, we will fix it soon.
