[kmonroe]

Howdy!

I’m running Tomcat 5.5, MyEclipse 3.8.4+QF2-Beta and Eclipse 3.1.0 M7.
When creating a JSP with intentional errors as per the Application Developer Guide tutorial, I do not see any validation errors in the IDE. I verified that validation is activated for the appropriate project.

Thx
Ken

[Riyad Kalla]

I’m running Tomcat 5.5, MyEclipse 3.8.4+QF2-Beta and Eclipse 3.1.0 M7.

Are you sure you are using the M7 compatiable build of MyEclipse? (it is in BETA).

Also to fix the validation, you need to have the “javac” executable in your system path, so that means putting your JDK’s bin directory in your PATH, preferablly at the front of it.

[kmonroe]

The MyEclipse build ID is:
200505151200-3.8.4+QF2-Betafor3.1M7

The Eclipse build ID is Eclipse 3.1.0 20050513-1415

The PATH statement contains the correct path to /bin/javac.exe

[Riyad Kalla]

The PATH statement contains the correct path to /bin/javac.exe

Your slashes are wrong, so I’m hoping you just typed them wrong… but we had two bug reports with this same issue and they had their slashses wrong… so let’s try this, open up a new console (Start > Run > cmd.exe) and type “java -version”, what do you get?

Also make sure you are opening your JSP files with the MyEclipse JSP Editor (right click on file > Open With > MyEclipse JSP Editor).

[kmonroe]

When I run java -version, I get “java version 1.5.0_01”. I double checked the PATH statement and the slashes are in the correct direction.

I double checked how I am opening the file also.

[Riyad Kalla]

Then let’s have a look at your log file:

1) Shut down MyEclipse
2) Erase <workspace dir>\.metadata\.log file
3) Start MyEclipse back upo, open a JSP file, add an error and save it, no validation markers?
4) Open the newly created .log file, paste the exceptions here if any.

**5) I would encourage you to upgrade to 1.5.0_03, while it seems to be a small increment, there were quite a few critical bug fixes between all of the services releases so far.

[kmonroe]

Deleted the .log file, created bad JSP, saved and got no validation errors. Also noticed that there is no new .log file in .metatdata. I’m going to install 1.5.0_03 and delete and reinstall Eclipse and MyEclipse

[Riyad Kalla]

Make sure to use a new workspace as well since all the information of E/ME is stored in the workspace.

[eCommerce]

I have the same problems. I made a clompletly new installation of Eclipse 3.1 M7 and MyEclipse 3.8.4 for M7. I only took the workspace from my old installation (Eclipse 3.01/MyEclipse 3.8.4). I haven’t any validation. I have installed JDK 1.42 – it should work with doesn’t it? You said to make a new workspace. How can I make an update without loosing all my worthful workspace informations?

Thanks for any help

[Riyad Kalla]

First try this:
http://www.myeclipseide.com/FAQ+index-myfaq-yes-id_cat-30.html#343

Then if that doesn’t work, try a new workspace by going to File > Switch Workspace > C:\testworkspace and see if the behavior works as it should, if it does, then you will likely need to create a new workspace and reimport all your projects.

[eCommerce]

Hi
Thanks for your answer but it didn’t help. The validation doesn’t work at all. I made an empty workspace and created a new JSP file I can put in the file what ever I want I do never get any error. It seems that it wouldn’t really check the file. If I compare the validation time with the older version it goes too fast. Maybe it will be better to work with the older version and wait for a stable release.

[Riyad Kalla]

Ahh, it sounds like the javac executable is not in your System path, these are exactly the symptoms when MyEclipse cannot find javac in order to compile and validate your JSP page.

I suggest editing your System PATH environment variable, and adding to the front of it the full path to your JDK’s BIN directory, something like:
c:\j2sdk1.4.2_08\bin;<REST OF PATH>

[eCommerce]

Hi Riyad
Thanks for your answer but it doesn’t work at all. I had already the path and with Eclipse 3.0.2 and MyEclipse 3.8.4 it works without any problem. It’s a pity.

[Riyad Kalla]

I had already the path and with Eclipse 3.0.2 and MyEclipse 3.8.4 it works without any problem. It’s a pity.

You likely have “java” in your system path, but you may not have your JDK’s bin directory in your system path. If you open up a console window and type “javac”, what do you get?

[khawes]

I’m having the same issue.
javac is on my path:
C:\eclipse>javac
Usage: javac <options> <source files>
where possible options include:
-g Generate all debugging info
-g:none Generate no debugging info
-g:{lines,vars,source} Generate only some debugging info
-nowarn Generate no warnings
-verbose Output messages about what the compiler is doing
-deprecation Output source locations where deprecated APIs are used
-classpath <path> Specify where to find user class files
-sourcepath <path> Specify where to find input source files
-bootclasspath <path> Override location of bootstrap class files
-extdirs <dirs> Override location of installed extensions
-d <directory> Specify where to place generated class files
-encoding <encoding> Specify character encoding used by source files
-source <release> Provide source compatibility with specified release
-target <release> Generate class files for specific VM version
-help Print a synopsis of standard options

[Author]

Posts