MyEclipse :: View topic - Bad class file [Closed]

MyEclipse: Bad class file [Closed]

rosana.rocha - Nov 05, 2004 - 02:20 PM
Post subject: Bad class file [Closed]

Hi,

I am having some trouble with the JSP validator.

I am having the following line in my JSP:

Code:

<%@ page import="com.upsscs.rmadcp.presentation.actions.Constants" %>

and the error message that I am receiving is:

Code:

cannot access com.upsscs.rmadcp.presentation.actions.Constants: bad class file: D:\dev\workspace\RmaThroughDcpWeb\src_web\WEB-INF\classes\com\upsscs\rmadcp\presentation\actions\Constants.class. NOTE: No JSP line number was avaliable so line 1 was used for the marker.

I checked the class file - it's there. I have rebuilt it to no avail. Does anyone have a clue??? The whole project is successfully deployed in Tomcat without any problem. The JSP in particular works fine.

I am using MyEclipse version 3.8.2 and Eclipse version 3.0.1.

Thanks!
Franck

support-rkalla - Nov 06, 2004 - 12:18 AM
Post subject:

Can you try cleaning the project and making sure that the class file is actually rebuilt? (check the timestamp)? I wonder why this would be happening...

support-scott - Nov 06, 2004 - 12:22 AM
Post subject:

Can you please post all the information we request in the Posting Guidelines thread at the top of this forum? That will give us some context so that we can determine what the problem might be. Thanks.

rosana.rocha - Nov 08, 2004 - 09:58 AM
Post subject:

Hi,

Yes I have cleaned my classes folder and checked the timestamps. That should all be fine.

What operating system and version are you running?
Windows 2000 Professional

What Eclipse version and build id are you using? (Help > About Eclipse Platform)
Version: 3.0.1
Build id: 200409161125

- Was Eclipse freshly installed for MyEclipse?
No. I first deinstalled MyEclipse 3.7(.2?), then I upgraded first Eclipse from 3.0 to 3.0.1 and then I installed MyEclipse 3.8.2. I have put up my web project from scratch again.

- If not, was it upgraded to its current version using the update manager?
Yes, I used the update manager. I followed the instructions that were put on the site by support-scott on Sep 26, 2004 - 02:32 PM. (I don't know the exact link anymore).

- Are any other external plugins installed?
Yes

- How many plugins in the <eclipse>/plugins directory are like org.eclipse.pde.*
14 (among which a few duplicates 3.0 and 3.0.1 directories)

What MyEclipse version are you using? (Help > About Eclipse Platform > Features)
3.8.2

What JDK version are you using to run Eclipse? (java -version)
1.4.2_04

What JDK version are you using to launch your application server?
1.4.2_04

What steps did you take that resulted in the issue?
This error did not occur in the 3.7 release of MyEclipse. After the upgrade it starts occurring. When I do a full clean (I even remove manually the classes directory under WEB_INF, the problem comes back after doing a rebuild within Eclipse

What application server are you using?
Tomcat. The application actually works fine.

Are there any exceptions in the Eclipse log file? (<workspace>/.metadata/.log)
Not any related to this problem

My system properties are:

Code:

*** System properties:
awt.toolkit=sun.awt.windows.WToolkit
eclipse.application=org.eclipse.ui.ide.workbench
eclipse.buildId=I200406251208
eclipse.commands=-os win32 -ws win32 -arch x86 -showsplash D:\eclipse30\eclipse.exe -showsplash 600 -exitdata D:\eclipse30\eclipse.exe -exitdata 134_88 -vm C:\WINNT\system32\javaw.exe
eclipse.product=org.eclipse.platform.ide
eclipse.startTime=1099906724232
eclipse.vm=C:\WINNT\system32\javaw.exe
eclipse.vmargs=-Xmx512M
-cp
D:\eclipse30\startup.jar
org.eclipse.core.launcher.Main

eof=eof
file.encoding=Cp1252
file.encoding.pkg=sun.io
file.separator=\
findbugs.home=/d:/eclipse30/plugins/edu.umd.cs.findbugs_0.8.1/
http.proxyHost=proxy.europe.ups.com
http.proxyPort=8080
http.proxySet=true
java.awt.graphicsenv=sun.awt.Win32GraphicsEnvironment
java.awt.printerjob=sun.awt.windows.WPrinterJob
java.class.path=D:\eclipse30\startup.jar
java.class.version=48.0
java.endorsed.dirs=C:\Program Files\Java\j2re1.4.2_04\lib\endorsed
java.ext.dirs=C:\Program Files\Java\j2re1.4.2_04\lib\ext
java.home=C:\Program Files\Java\j2re1.4.2_04
java.io.tmpdir=C:\DOCUME~1\fdbruijn\LOCALS~1\Temp\
java.library.path=C:\WINNT\system32;.;C:\WINNT\system32;C:\WINNT;D:\oracle\ora81\bin;D:\oracle\ora81\Apache\Perl\5.00503\bin\mswin32-x86;C:\Program Files\Oracle\jre\1.1.7\bin;C:\PROGRA~1\PVCS\vm\win32\bin;C:\PROGRA~1\PVCS\vm\common\bin\win32;C:\WINNT\system32;C:\WINNT;C:\WINNT\System32\Wbem;C:\Program Files\Common Files\Adaptec Shared\System;C:\Program Files\SilverStream\eXtendAppServer\bin;C:\Program Files\Microsoft SQL Server\80\Tools\Binn\;D:\dev\apps\apache-ant-1.6.2\bin\
java.runtime.name=Java(TM) 2 Runtime Environment, Standard Edition
java.runtime.version=1.4.2_04-b05
java.specification.name=Java Platform API Specification
java.specification.vendor=Sun Microsystems Inc.
java.specification.version=1.4
java.util.prefs.PreferencesFactory=java.util.prefs.WindowsPreferencesFactory
java.vendor=Sun Microsystems Inc.
java.vendor.url=http://java.sun.com/
java.vendor.url.bug=http://java.sun.com/cgi-bin/bugreport.cgi
java.version=1.4.2_04
java.vm.info=mixed mode
java.vm.name=Java HotSpot(TM) Client VM
java.vm.specification.name=Java Virtual Machine Specification
java.vm.specification.vendor=Sun Microsystems Inc.
java.vm.specification.version=1.0
java.vm.vendor=Sun Microsystems Inc.
java.vm.version=1.4.2_04-b05
line.separator=

Thanks in advance,
Franck

rosana.rocha - Nov 08, 2004 - 10:11 AM
Post subject:

Hi,

I have been able to solve the problem.

Although Eclipse was running with JDK 1.4.2_04, it was using the javaw.exe stored in the Windows directory (see my properties in my previous post).

I forced Eclipse to use the JDK in the installation directory through the -vm startup parameter, and the error does not appear anymore.

It could be that this has to do with the difference of a JRE compared to a JDK. A JRE does not have javac (compiler), while the JDK has. But I might be wrong.

Cheers,
Franck

support-rkalla - Nov 08, 2004 - 02:07 PM
Post subject:

Franck,
Thank you for the followup and running this down successfully.

dmoir - Sep 08, 2006 - 06:18 PM
Post subject:

A footnote: I received the message "No JSP line number was avaliable so line 1 was used for the marker" in a project I was working on. It turned out that there was a conflict with Quick Test Pro software installed on my machine. Uninstalling Quick Test Pro solved the problem.