[
https://issues.jboss.org/browse/JBIDE-9587?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-9587:
----------------------------------------------
Verification is migrated to WTP validation (see JBIDE-10190). I supported dependencies in
incremental validation, and we can replace it with full validation for the case of class
path changes.
By the way, WTP validation in Eclipse 3.7 includes JSF Application Configuration
Validator, it contains checks of class references (our validator also checks navigation
rules), and it does not supports dependencies in incremental validation, at least in the
current version. So, maybe in the future we will have to drop our validation of
faces-config.xml, or each problem will be presented by two markers.
Obsolete verify-errors of faces-config.xml after classpathchanges
-----------------------------------------------------------------
Key: JBIDE-9587
URL:
https://issues.jboss.org/browse/JBIDE-9587
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JSF
Affects Versions: 3.2.1.Final
Reporter: Peter Rader
Assignee: Viacheslav Kabanovich
Priority: Minor
Fix For: LATER
Original Estimate: 2 days
Remaining Estimate: 2 days
The verification of faces-config.xml does not run after Classpathchanges.
On an jsf-project without jsf-librarys, the error occources correctly "error:
Attribute converter-class references to XXX that does not implement interface
javax.faces.convert.Converter".
Then, if you add the jsf-librarys to the classpath, the "Verification Problem"
"error: Attribute converter-class references to XXX that does not implement interface
javax.faces.convert.Converter" is NOT removed!
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira