[ https://issues.jboss.org/browse/SEAMFORGE-156?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-156. ---------------------------------------- Assignee: Lincoln Baxter III Resolution: Done done -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

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

The second possibility looks nicer. I'd choose that instead of the first one. "doSearch" isn't that intuitive IMHO. Best Regards, George Gastaldi Em 09/09/2012, às 11:39, "Lincoln Baxter, III" <lincolnbaxter(a)gmail.com&gt; escreveu:

You are the man :) On Sun, Sep 9, 2012 at 1:02 PM, Thomas Frühbeck <fruehbeck(a)aon.at&gt; wrote: -- Lincoln Baxter, III http://ocpsoft.org "Simpler is better."

[ https://issues.jboss.org/browse/SEAMFORGE-156?page=com.atlassian.jira.plu... ] Richard Kennard edited comment on SEAMFORGE-156 at 5/2/11 7:45 PM: ------------------------------------------------------------------- Note an equally 'correct' thing to do (and much easier :) might be to just stay with metawidget-all, and wait for AS 7 to fix their bug. It is, after all, a serious bug that will need to be fixed for more than just Metawidget. I can't imagine AS 7 can go 'final' without fixing it. The bug is related to JBoss classpath scanning not properly ignoring missing classes. JBoss AS 6 had a similar thing. There, you could configure which errors to ignore in scanning-deployers-jboss-beans.xml. I believe Jason Porter was filing a JIRA? was (Author: kennardconsulting): Note an equally 'correct' thing to do (and much easier :) might be to just stay with metawidget-all, and wait for AS 7 to fix their bug. It is, after all, a serious bug that will need to be fixed for more than just Metawidget. I can't imagine AS 7 can go 'final' without fixing it. The bug is related to JBoss classpath scanning not properly ignoring errors. JBoss AS 6 had a similar thing. There, you could configure which errors to ignore in scanning-deployers-jboss-beans.xml. I believe Jason Porter was filing a JIRA? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFORGE-156?page=com.atlassian.jira.plu... ] Richard Kennard edited comment on SEAMFORGE-156 at 5/2/11 7:46 PM: ------------------------------------------------------------------- Note an equally 'correct' thing to do (and much easier :) might be to just stay with metawidget-all, and wait for AS 7 to fix their bug. It is, after all, a serious bug that will need to be fixed for more than just Metawidget. I can't imagine AS 7 can go 'final' without fixing it. The bug is related to JBoss classpath scanning not properly ignoring missing classes. JBoss AS 6 had a similar thing. There, you could configure which errors to ignore in scanning-deployers-jboss-beans.xml (and it would ignore NoClassDefFoundError by default). I believe Jason Porter was filing a JIRA? was (Author: kennardconsulting): Note an equally 'correct' thing to do (and much easier :) might be to just stay with metawidget-all, and wait for AS 7 to fix their bug. It is, after all, a serious bug that will need to be fixed for more than just Metawidget. I can't imagine AS 7 can go 'final' without fixing it. The bug is related to JBoss classpath scanning not properly ignoring missing classes. JBoss AS 6 had a similar thing. There, you could configure which errors to ignore in scanning-deployers-jboss-beans.xml. I believe Jason Porter was filing a JIRA? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFORGE-156?page=com.atlassian.jira.plu... ] Richard Kennard commented on SEAMFORGE-156: ------------------------------------------- Actually I'd rather just go with metawidget-all. It's far cleaner for those learning Metawidget (just a single entry in the POM) and easier on Seam Forge too. I'd be much more interested in getting the AS 7 issue resolved, because this will impact all my tutorials and examples too. They all use metawidget-all, because it is an easier initial learning curve. Really only power users will want the fine-grained dependencies of metawidget-faces, metawidget-jpa etc. Does Jason have a link to the JIRA for the AS 7 issue? -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFORGE-156?page=com.atlassian.jira.plu... ] Lincoln Baxter III closed SEAMFORGE-156. ---------------------------------------- Resolution: Won't Fix Will have to wait for AS7 to fix this. Closing as not a Forge issue. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://issues.jboss.org/browse/SEAMFORGE-156?page=com.atlassian.jira.plu... ] Torsten Fink commented on SEAMFORGE-156: ---------------------------------------- As a workaround you can remove the metawidget-all dependency and replace it with the following ones. After that I could run the application on AS 7. {code} ... <properties> <metawidget.version>1.20</metawidget.version> </properties> <dependencies> .... <dependency> <groupId>org.metawidget.modules.faces</groupId> <artifactId>metawidget-faces</artifactId> <version>${metawidget.version}</version> </dependency> <dependency> <groupId>org.metawidget.modules</groupId> <artifactId>metawidget-annotation</artifactId> <version>${metawidget.version}</version> </dependency> <dependency> <groupId>org.metawidget.modules</groupId> <artifactId>metawidget-java5</artifactId> <version>${metawidget.version}</version> </dependency> <dependency> <groupId>org.metawidget.modules</groupId> <artifactId>metawidget-jpa</artifactId> <version>${metawidget.version}</version> </dependency> <dependency> <groupId>org.metawidget.modules</groupId> <artifactId>metawidget-beanvalidation</artifactId> <version>${metawidget.version}</version> </dependency> ... </dependencies> ... {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira