[jboss-jira] [JBoss JIRA] (JBEE-145) Missing validationFailed and isValidationFailed Methods in FacesContext
[
https://issues.jboss.org/browse/JBEE-145?page=com.atlassian.jira.plugin.s...
]
Kay Wrobel commented on JBEE-145:
---------------------------------
You can close this bug. It seems the NetBeans IDE erroneously puts the older JAR in front
of the newer jar in the class path for the project inside project.properties. I manually
moved the jar references around and can now enjoy my application on JBoss. Maybe it is
because alphabetically, the older jar sits in front of the newer jar?
Missing validationFailed and isValidationFailed Methods in
FacesContext
-----------------------------------------------------------------------
Key: JBEE-145
URL: https://issues.jboss.org/browse/JBEE-145
Project: JBoss JavaEE Spec APIs
Issue Type: Bug
Components: jboss-jsf-api
Environment: Debian GNU Linux 7 64-Bit
Java: 1.7.0_25; OpenJDK 64-Bit Server VM 23.7-b01
Runtime: OpenJDK Runtime Environment 1.7.0_25-b30
System: Linux version 3.2.0-4-amd64 running on amd64; UTF-8; en_US (nb)
JBoss 7.1.1 Final
Reporter: Kay Wrobel
Assignee: Shelly McGowan
Labels: FacesContext, JSF2
I have a NetBeans module called PrimeFaces CRUD Generator. One thing I do when an error
was detected on a page is add a FacesMessage to the current FacesContext and the
invalidate the page with validationFailed() method. My IDE (NetBeans 7.4) cannot compile
this code because of missing symbols for validationFailed and isValidationFailed for
javax.faces.context.FacesContext. These are supposed to be there according to Oracle Java
EE 6 Spec.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira