[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9587) Obsolete verify-errors of faces-config.xml after classpathchanges
[
https://issues.jboss.org/browse/JBIDE-9587?page=com.atlassian.jira.plugin...
]
Viacheslav Kabanovich commented on JBIDE-9587:
----------------------------------------------
It is our verification. It does not keep links between faces-config.xml and Java so that
when *.java file or classpath is changed, xml is not revalidated. The best way is to drop
the verification framework and to reimplement the validation rules with wtp's
validation framework that we have for seam and cdi.
We have 30 rules for faces-config.xml, 10 rules for struts-config.xml, 19 rules for
web.xml. Our old framework is really obsolete and inefficient; and anyway it is redundant
to use both it and wtp's validation, "There Can Be Only One".
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: 3.3.x
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.
For more information on JIRA, see: http://www.atlassian.com/software/jira