[jboss-jira] [JBoss JIRA] (JBCOMMON-125) JBOSS 7.0.2 Final doesn't recognize EL 2.2 parameterized method calls

[Arron Ferguson (Created) (JIRA)]

JBOSS 7.0.2 Final doesn't recognize EL 2.2 parameterized method calls
---------------------------------------------------------------------

                 Key: JBCOMMON-125
                 URL: https://issues.jboss.org/browse/JBCOMMON-125
             Project: JBoss Common
          Issue Type: Bug
      Security Level: Public (Everyone can see)
          Components: common-core (2.x)
    Affects Versions: 2.2.18.GA 
         Environment: Windows 7, 64 bit, JDK/RE 7 (Java(TM) SE Runtime Environment (build 1.7.0-b147))
            Reporter: Arron Ferguson


Attempting to run a web app that utilizes EL 2.2 parameterized method calls results in JBoss mistakenly interpreting them as properties and results in javax.el.PropertyNotFoundException exceptions. E.g.:

This class:
import java.util.Date;
import javax.enterprise.context.RequestScoped;
import javax.inject.Named;

@Named("serverTime")
@RequestScoped
public class DateMessager {
    public String getDate() {
        return new Date().toString();
    }
}

Being used in an h:outputText:

<h:outputText value="#{serverTime.getDate()}" id="time"/>

Results in an error message:
16:05:39,856 SEVERE [javax.enterprise.resource.webcontainer.jsf.application] (http--127.0.0.1-8080-1) Error Rendering View[/index.xhtml]: javax.el.PropertyNotFoundException: /index.xhtml @29,70 value="#{serverTime.getDate()}": The class 'org.jboss.weld.proxies.DateMessager$Proxy$_$$_WeldClientProxy' does not have the property 'getDate'.

I've ensured that the web.xml is referring to the correct version of servlets:
<web-app version="3.0" xmlns="http://java.sun.com/xml/ns/javaee"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
  xsi:schemaLocation="http://java.sun.com/xml/ns/javaee http://java.sun.com/xml/ns/javaee/web-app_3_0.xsd">
...
</web-app>

Note: this works flawlessly in Glassfish 3.1.1 with no errors.

--
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