[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-3378) Seam EL validation does not use same technique as the EL resolver (Continued)

> The fundamental problem is that the rules of validation are not the same as a running app.

Seam EL validation does not use same technique as the EL resolver (Continued) ----------------------------------------------------------------------------- Key: JBIDE-3378 URL: https://jira.jboss.org/jira/browse/JBIDE-3378 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 2.1.2, 3.0.0.alpha, 3.0.0.beta1 Environment: Latest nightly build of JBoss Tools. On eclipse 3.4 SR1. JSF/Facelets/Richfaces/Seam 2.1.x environment Reporter: Tim Evers JBoss Tools does not validate method EL expressions properly if the method name starts with 'is' If I have a method in my SEAM bean like this. public boolean isEditButtonDisplayed() { return true; //removed what this method actually does for example } and then I have in my xhtml this: <gekko:commandButton id="tenureEditButton" value="Edit" action="#{TenureKeyController.editButtonClicked()}" rendered="#{TenureKeyController.isEditButtonDisplayed()}" /> When I validate this it says: "isEditButtonDisplayed" cannot be resolved. It looks like when the validation method sees the word 'is' it automatically thinks that the expression is a value expression. This should not be the case. Infact if I end my expression witih '()' it should always look for a method. The behaviour of the EL validation should be exactly the same as what happens when I run the system. But this is not what is happening. If I change my code to what the JBoss Tools autocomplete says to it actually breaks the application. According to JBoss Tools it says I should have this. <gekko:commandButton id="tenureEditButton" value="Edit" action="#{TenureKeyController.editButtonClicked()}" rendered="#{TenureKeyController.editButtonDisplayed}" /> Which of course will not work when the app is deployed. This is somewhat related to: https://jira.jboss.org/jira/browse/JBIDE-2673 just a different scenario. The fundamental problem is that the rules of validation are not the same as a running app.