[forge-dev] faces-scaffold: generated app breaks on ambiguity of property search and method search() when Seam Faces present

Lincoln Baxter, III lincolnbaxter at gmail.com
Sun Sep 9 10:39:23 EDT 2012

Ooooh that's an unfortunate problem! We can certainly change this, though.
I personally like the idea of "doSearch()" because it is more descriptive
than "example". WDYT?


On Sun, Sep 9, 2012 at 5:39 AM, Thomas Frühbeck <fruehbeck at aon.at> wrote:

>  Hi,
> just found a subtle problem in the generated faces application.
> The backing beans carry the property "search" for form field based dynamic
> query and the method search() to invoke the selection.
> After adding Seam3 Faces module to the project the application fails on
> "Search" because the ELResolver will take the method search() instead of
> the property "search" first:
> Caused by: javax.el.PropertyNotFoundException: /searchTest/search.xhtml
> @34,90 value="#{searchTestBean.search.name}": Target Unreachable,
> 'search' returned null
> So I see 2 possibilities for remedy:
>     1. rename method "search()" to sth. like "doSearch()"
>     2. rename property "search" to "example"
> I personally like second poss. more, because it matches the kinda
> "query-by-example" mechanism and the method name "search()" is most
> descriptive.
> Any ideas welcome!
> Thomas
> _______________________________________________
> forge-dev mailing list
> forge-dev at lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/forge-dev

Lincoln Baxter, III
"Simpler is better."
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.jboss.org/pipermail/forge-dev/attachments/20120909/84421f09/attachment.html 

More information about the forge-dev mailing list