Hello everybody;

This should fit in -Success Story- :D

A couple of weeks ago; I was wondering how to make MyEclipse to Syntax Check my JSPs; I have found that in

Preferences --> MyEclipse --> Editors --> JSP/HTML Editor --> General

is a radio button [which is selected] indicating to Compile JSPs

But even If I put non-sense text in the JSP; there were no indication of the syntax error. (The Code Completion works just Fine!).

Then I've Installed LOMBOZ Plugin; and re-configured eclipse to keep MyEclipse as the Default JSP Editor.

And then I've got Syntax Checking Working! :)

==== Up to This Far goes the Success Story :) ======

That works fine for me, but leave me the question:

Why Eclipse is calling the Lomboz Syntax Check when the Editor used to open the JSPs is MyEclipse JSP Editor?

I have double check that I am actually using the MyEclipse JSP Editor istead of the Lomboz One.

BTW: Im Using MyEclipse 3.0M6

Saludos

Alejandro

Alejandro,
Can you give us an example of the "nonsense" text that you were typing into the page originally that was not being marked as an error, and then show what Lomboz is marking as an error?

This sounds very strange...

Aparently there are some incompatabilities with Lomboz and MyEclipse that could explain why you are seeing this cross-over behavior. Unfortunately this is not a support configuration, and to help avoid any conflicts, I would suggest using the products in separate installations of Eclispe to avoid any further conflicts.

While it might seem great that the current conflict is more accurate error checking, you might run into problems down the road with wizards not working or deployments failing and not be sure why. Our first suggestion would to be to get rid of all conflicting plugins (Lomboz being one of them and XML Buddy/XMen/JBossIDE being others). These conflicts stem from the fact that sometimes our plugins are branches from these open source projects and conflicts occur, and other times its just a functionality conflict (i.e. one plugin will take the file association for a certain file type, and you won't get the full MyEclipse experience).

Hello;

I Have made the folowing Test:

Extracted : eclipse-SDK-3.0M6-win32.zip
Installed : EnterpriseWorkbenchInstaller_030700RC2.exe
Copied : templates_es.properties to <MyEclipse-Dir>\plugins\com.genuitec.eclipse.wizards_3.6.200
Run: : eclipse.exe
Checked : MyEclipse Perspective EXISTS

Case One
========
Create : New J2EE Web Project
Create : New JSP : One.jsp
Checked : Syntax Check on One.jsp is OK (added garbage; and MyEclipse noticed it)

Case Two
========
Create : New Simple Project
Team : Selected TEAM -> Share-Project
Update : TEAM --> Update : get Latest Version
Checked : Opened *any* JSP; add garbage ("asd ad asd ad ad;")
Checked : There is no message or mark of Syntax Error.

After Checking-Out the project from CVS; I have noticed that the option (with Right-Click on the Project Root) MyEclipse --> Add-WebProject-Capabilities is disabled; the I could not test putting that option on.

The reason I have selected Simple-Project is because in this project the directory structure is kinda messy; and I have to set manually where are the source folders and so on.

If I Select Enterprise Application Project; the wizard forces me to define a Web-App and at least One EJB; leaving a differerent directory structure from what the application haves.

Then maybe the question would be:

How can I tell MyEclipse to Perform JSP Syntax Checking if I have started with a Simple Project ?

-----------

Sorry for the topic tweak; started from a -Success Story- and ended with one more -Support- issue :oops:

Saludos

Alejandro

Alejandro,

The example with a simple project won't work because it is not a java project and not a web project. This basically means that the Java project builder is not active for the project and it is within this build loop that all the syntax checking and validation is performed. Without the builder, nothing can happen.

To get what you want, you really need to develop your JSP's within a MyEclipse Web project.

Ok, Thanks!


Saludos