- This topic has 5 replies, 2 voices, and was last updated 21 years ago by kaig1969.
-
AuthorPosts
-
kaig1969MemberI have a JSP file which has this first line:
<%@ taglib prefix=”c” uri=”http://java.sun.com/jstl/core” %>
This line is marked and the Problems view shows the following problems:
Severity Description Resource In Folder Location Creation Time
de.bb cannot be resolved or is not a valid superclass
OutlookRememberWidth.jsp
ev-div/evITA-Web/jsp/outlook line 1 13. November 2003 18:42:37Severity Description Resource In Folder Location Creation Time
The method getPageContext(Servlet, ServletRequest, ServletResponse,
String, boolean, int, boolean) in the type JspFactory is not applicable
for the arguments (_OutlookRememberWidth$002ejsp$, HttpServletRequest,
HttpServletResponse, null, boolean, int, boolean)
OutlookRememberWidth.jsp
ev-div/evITA-Web/jsp/outlook line 1 13. November 2003 18:42:37Severity Description Resource In Folder Location Creation Time
The method getServletConfig() is undefined for the type
_OutlookRememberWidth$002ejsp$ OutlookRememberWidth.jsp
ev-div/evITA-Web/jsp/outlook line 1 13. November 2003 18:42:37Now you’re saying this is little information. You’re right. My problem is that I don’t have the foggiest idea how to go about debugging this.
Of course, I’m trying to be a good boy so I tried to make a test case, but of course in the test project the same line doesn’t show any error.
Should I investigate the WEB-INF/lib directory and try to remove some jars from it to see if there are any conflicts? There are about a dozen of them and nobody really knows which ones are actually used… I wonder if there is a way to find out which ones are used?
Using MyEclipse 3.6.4 with Eclipse 3.0M4.
tia,
Kai
kaig1969MemberI forgot to mention that the *.jsp file in question works fine, when using it in Tomcat 5.0.12.
Also, there is a typo in the subject; I meant *.jsp not *.js.
kaig1969MemberI just looked in my workspace, and there is just one occurrence of the string “de.bb” in each of my projects. It’s this snippet from the .project file:
<buildCommand>
<name>de.bb.bje.eclipse.IncrementalJspBuilder</name>
<arguments>
</arguments>
</buildCommand>Hm.
kaig1969MemberNow I found a nice little test case: enter the following into a JSP file in any project:
<jsp:useBean id=”x” scope=”session” class=”java.lang.String” />
<jsp:setProperty name=”x” property=”*”/>It’s the property=”*” that’s triggering the trouble. Most fascinating.
Is it a bug?
support-michaelKeymasterYes this is a duplicate bug report to:
https://www.genuitec.com/forums/topic/myeclipse-2-6-4-jsp-setproperty-closed/
We’ll have a fix for this in the next week or so.
Michael
MyEclipse Support -
AuthorPosts