[seam-issues] [JBoss JIRA] (SEAMFACES-246) CollectionsELResolver should consider property before method

[Kris Vandebroek (JIRA)]

Kris Vandebroek created SEAMFACES-246:
-----------------------------------------

             Summary: CollectionsELResolver should consider property before method
                 Key: SEAMFACES-246
                 URL: https://issues.jboss.org/browse/SEAMFACES-246
             Project: Seam Faces
          Issue Type: Bug
            Reporter: Kris Vandebroek


Problem:

The CollectionsELResolver makes following assumption: if the 'base' is not a collection, map or datamodel invoke the method with name 'property'.
However if property = foo and the base class has a method getFoo() and foo(), the first one should be called.

Scenario:

I have a JSF 2.0 page, containing:

{code}
<ui:param value="#{myController.filter}" name="filter"/>
{code}

In my @Named MyController, I have a property filter with a getFilter() method. But I also have a filter() method which is called when my filter form is submitted:

{code}
<p:commandButton value="#{msg.general_button_filter_search}" action="#{myController.filter()}" />
{code}

Without Seam Faces (and thus without the CollectionsELResolver) the above code works. For the param the method getFilter() is called and for the action the method filter() is called.
With Seam Faces, the CollectionsELResolver comes quite early in the CompositeELResolver chain, and invokes for the param also the filter() method.

(Possibly related with SEAMFACES-208)

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