| Summary: | toggling validate JSP Fragments not functioning | ||
|---|---|---|---|
| Product: | [WebTools] WTP Source Editing | Reporter: | Brian Gardner <brian> |
| Component: | jst.jsp | Assignee: | Ian Tewksbury <itewksbu> |
| Status: | RESOLVED DUPLICATE | QA Contact: | Nitin Dahyabhai <thatnitind> |
| Severity: | normal | ||
| Priority: | P3 | CC: | andy.j.peterson, thatnitind |
| Version: | 3.0.1 | ||
| Target Milestone: | --- | ||
| Hardware: | Macintosh | ||
| OS: | Mac OS X - Carbon (unsup.) | ||
| URL: | http://www.experts-exchange.com | ||
| Whiteboard: | |||
|
Description
Brian Gardner
Usually JSP fragments are expected to be named .jspf. .jsf files are expected to be JavaServer Faces files. Are you sure? If I go to General->Content Types->Text->JSP->JSP Fragment I see *.jsf (locked) *.jspf (locked) Further more I have a setup that's near identical on Windows and the .jsf extensions do the trick. Brian's right. If I had to guess, something's amiss in org.eclipse.jst.jsp.core.internal.validation.JSPBatchValidator.isFragment(IFile)or its caller. Brian, can you attach a sample file that's being validated regardless of the preference setting? I am having the same issue on windows version. Not the best workaround, but what I've done to rectify the problem. Right click on main project on Project Expolorer or Navaigator and select the properties option. Choose the Validation option. You have the option to change this in your project prefs or globally if you prefer, I did per project settings so they would be stored in version control. Click the ... (elipse) and remove .jsf files from the include list for the validators "JSP Content Validator" and "JSP Syntax Validator". Now right click on the mainApp again and select the validate option. Good luck! *** This bug has been marked as a duplicate of bug 250833 *** |