[Idefix]

Hi,

I just updated my JDK to the new Sun JDK 1.5 SE and things are fine, but validation … it doesn’t seem to handle jspf (fragments) properly anymore.

The only thing I did was to replace the JDK, launch eclipse, edit preferences and rebuild/revalidate my project … result -> All but one JSPF fragments are marked with tons of problems (warnings and errors). The one fragment that shows no complaints has it’s content fully enclosed in a <logic> tag, so I guess that’s why.

Oh, the complaints in the fragments are about all html code …

Is this known, or just me?

Thanks,
Chris

[Scott Anderson]

Chris,

You can turn off HTML validation at Window > Preferences > MyEclipse > Validation. Also, be sure the suffix(es) you use for jsp fragments are entered properly under Window > Preferences > MyEclipse > Editors > JSP.

[Idefix]

Well, this is what I already did … but I don’t really get why it was working properly before?!?

I did not change anything besides the JDK upgrade … well, and launching “eclipse -clean” to have it use the new JDK

Thanks,
Chris

[Riyad Kalla]

If these are all HTML validation errors (stuff like “<tr> must be contained in a <tbody> tag”) can you right click on your project, go down to MyEclipse and click the “Remove validation errors” option and then rebuild the project (With HTML validation off)?

Also double check your project Validation settings, they might be overriding the global validation settings (right click project, Properties, MyEclipse-Validation).

[Idefix]

Sorry, I didn’t make clear what I meant …

I disabled HTML validation in the meantime and this works. But I’d like to understand why I didn’t have to disable HTML validation before!?!

Before upgrading the JDK, HTML validation was enabled and didn’t complain in JSPF fragment files, even so the HTML code in this files is incomplete as it’s split over several files …
Now, after upgrading the JDK, validation fails with this HTML code … that’s what bothers me, the before/after effect 😉

Thanks,
Chris

[Riyad Kalla]

Chris,
We used to ship with HTML validation off by default, now I believe its on… its possible that in conjunction with your JDK upgrade, the setting for HTML flaked out and it got turned on somehow.. no biggie. I keep mine turned off too because the projects I work on are definately not HTML 4.01 compliant and I don’t want to stare at all the warnings 😉

[Author]

Posts