- This topic has 8 replies, 6 voices, and was last updated 21 years ago by
.
-
Posts
-
MyEclipse 2.6.4 is showing errors for a simple JSP.
My setup:
Windows XP Professional SP 1
Eclipse 2.1.2 Build 200311030802
Eclipse freshly installed
7 org.eclipse.pde.* directories
MyEclipse 2.6.4
No other external plugins
J2SDK 1.4.1_02
Tomcat 4.1.27 launched with J2SDK 1.4.1_02I created:
a new Web Module Project called JSPTest.
a bean called TedBean with two fields (String name, int age)
a JSP called MyJspIn the JSP, just after <body> I have:
<jsp:useBean id=”tedBean” class=”com.foye.TedBean” scope=”session” />
<jsp:setProperty name=”tedBean” property=”*”/>The first line, which is blank and the <jsp:setProperty…/> line are marked with errors.
The Tasks view shows:
“de cannot be resolved or is not a valid superclass” for line 1
“The method getPageContext(Servlet, ServletRequest, ServletResponse, String, boolean, int, boolean) in the type JspFactory is not applicable for the arguments (_MyJsp$002ejsp$, HttpServletRequest, HttpServletResponse, null, boolean, int, boolean)” for line 1
“The method getServletConfig() is undefined for the type _MyJsp$002ejsp$” for line 1
“de cannot be resolved” line 29 (the line with property=”*”)
Ted
I was able to replicate this behavior and have entered it in our issue tracking system. Expect a fix for this issue well before the end of the month.
Michael
MyEclipse SupportJust an ‘FYI’, I am also getting this pesky bug.
Will this be fixed in the 3.0M5 (11/21/2003) matching release, or is there a patch I can apply?
— Justin
Justin,
It will be fixed in the next release (3.7) that is targeted at the M5 build.
–Scott
MyEclipse SupportWhen will the fixed Version be released?
This bug is really annoying in the project I’m currently working on.
Isn’t there a workaround for this?regards,
RickHi Rick,
I empathize with you on this nagging problem. I’m not aware of a work-around for this release. I’m helping test the next release this week with the expectation that it will roll out early next week. We are moving as quickly as possible while trying to increase quality.
Michael
MyEclipse SupportD,
I’m not sure what you mean at this point. I just tried 2.7 RC1 with this:
<jsp:useBean id="tedBean" class="java.lang.String" scope="session" /> <jsp:setProperty name="tedBean" property="*"/>and it compiled it just fine. When I changed it to this:
<jsp:useBean id="tedBean" class="java.lang.String" scope="session" /> <jsp:setProperty name="tedBean" property="badField"/>I received a proper compiler error that setBadField didn’t exist.
What specifically are you experiencing that you think should be different?
–Scott
MyEclipse SupportHi,
My mistake, it’s working fine.
However, if you load a 2.6.4 project into the 2.7 environment the errors shown in the project in 2.6.4 get carried over to 2.7 (e.g. the erroneous error under discussion).
To workaround this you need to make an arbitrary edit to the file when using 2.7 (e.g. insert and then delete a space) and then save it. When you do that MyEclipse will re-evaluate the “errors” on your page, and then remove them.
HTH
D.
