[seam-issues] [JBoss JIRA] (JBSEAM-4979) Seam 2.3.0.Beta2 breaks EL resolution in JSF

[Andrea Martino (JIRA)]

Andrea Martino created JBSEAM-4979:
--------------------------------------

             Summary: Seam 2.3.0.Beta2 breaks EL resolution in JSF
                 Key: JBSEAM-4979
                 URL: https://issues.jboss.org/browse/JBSEAM-4979
             Project: Seam 2
          Issue Type: Bug
          Components: JSF Integration
    Affects Versions: 2.3.0.BETA2
         Environment: JBOSS AS 7.1.1. + RichFaces 4.2.2.Final + Seam 2.3.0.Beta2
            Reporter: Andrea Martino


Accessing the method of a bean without the ending brackets breaks property resolution.

In Seam 2.3.0.Beta1 the following is valid and works fine. The action attribute of <s:link> tag references test.init without ending brackets.
{code:xml}
<s:link view="/test.xhtml" propagation="none" action="#{test.init}" value="Test" />
{code}

The above code does not work in Seam 2.3.0.Beta2. In order to have it working in Beta2, the following must be used:
{code:xml}
<s:link view="/test.xhtml" propagation="none" action="#{test.init()}" value="Test" />
{code}

If no brackets are added to the method name, the following is logged to the console:
{code:title=Log file|borderStyle=solid}
17:19:43,181 SCHWERWIEGEND [javax.enterprise.resource.webcontainer.jsf.application] (http-localhost-127.0.0.1-8080-1) Error Rendering View[/menu.xhtml]: javax.el.ELException: /menu.xhtml: The class 'com.example.Test_$$_javassist_seam_66' does not have the property 'init'.
	at com.sun.faces.facelets.compiler.AttributeInstruction.write(AttributeInstruction.java:94) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.facelets.compiler.UIInstructions.encodeBegin(UIInstructions.java:82) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at com.sun.faces.facelets.compiler.UILeaf.encodeAll(UILeaf.java:183) [jsf-impl-2.1.7-jbossorg-2.jar:]
	at javax.faces.component.UIComponent.encodeAll(UIComponent.java:1782) [jboss-jsf-api_2.1_spec-2.0.1.Final.jar:
{code}

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