[ http://jira.jboss.com/jira/browse/JBSEAM-2597?page=all ] Gavin King closed JBSEAM-2597. ------------------------------ Resolution: Cannot Reproduce Bug This report is vague and anyway does not refer to behavior of Seam itself. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2597?page=all ] Christian Bauer reopened JBSEAM-2597: ------------------------------------- I can't reproduce the issue Pete mentioned, Facelets does not swallow an exception on rendered="{bindingThrowsException}", at least not during a regular GET request. However, the JSF RI + Seam swallow exceptions in two other situations: 1. Exception on POSTback thrown in UPDATE MODEL in a value-binding setter. This is converted, without messages in the log, to a JSF validation error message that says "Error writing 'formContent' on type org.jboss.seam.wiki.core.action.DocumentHome_$$_javassist_29". No stacktrace or other hint in the log. 2. Exception on POSTback from an Ajax4JSF request thrown in UPDATE MODEL in a value binding setter. This is also converted, but if you do not reRender the message section of your page, nothing will appear on the page but this in the log: INFO [javax.enterprise.resource.webcontainer.jsf.lifecycle] WARNING: FacesMessage(s) have been enqueued, but may not have been displayed. sourceId=docEditForm:previewSwitch[severity=(ERROR 2), summary=(/docEdit_d.xhtml @191,158 value="#{documentHome.enabledPreview}": Error writing 'enabledPreview' on type org.jboss.seam.wiki.core.action.DocumentHome_$$_javassist_20), detail=(/docEdit_d.xhtml @191,158 value="#{documentHome.enabledPreview}": Error writing 'enabledPreview' on type org.jboss.seam.wiki.core.action.DocumentHome_$$_javassist_20)] Obviously 1. and 2. are connected, so this is, as hinted in the original issue summary, about JSF swallowing exceptions in UPDATE MODEL and converting them into weak message that might be displayed in different places. Now, I don't know why the JSF RI authors decided that a RuntimeException can be ignored and that processing can continue after the UPDATE MODEL phase clearly failed. Even if we can't do anything about this in Seam, we should leave this issue open until this is resolved in one way or another. Note: I've already updated Seam with Petes new JDK/log4j logging bridge, so that INFO message that says "WARNING" is just... wrong. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2597?page=comments#action_12399903 ] Pete Muir commented on JBSEAM-2597: ----------------------------------- 2) is to be expected given the way ajax4jsf works (doesn't automatically add anything to the rerender. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2597?page=all ] Pete Muir updated JBSEAM-2597: ------------------------------ Fix Version/s: 2.1.0.GA (was: 2.1.0.BETA1) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ http://jira.jboss.com/jira/browse/JBSEAM-2597?page=comments#action_12413285 ] asookazian commented on JBSEAM-2597: ------------------------------------ I am experiencing a problem using Seam 2.0.1.GA that is related to this one. Involves using h:selectBooleanCheckbox component embedded in a h:dataTable. Works fine as POC mod in the hotel booking example. When I implemented the @Transient solution to the entity class, etc. now I consistently see the following error in the h:messages component of my rendered facelet: /testMultiCheckbox.xhtml @40,62 value="#{hardware.selected}": Error writing 'selected' on type com.cox.shims.entity.TbHardware I have posted this on the forum as: http://seamframework.org/Community/JSFExceptionBeingSwallowedNeedHelpPlz There is no exception/stack trace in the server.log and I cannot identify the root cause of the problem. I've spent several hours troubleshooting this problem to no avail. When I click the submit commandButton, the submit() method is not being exec'd due to this error I presume. If in this case as well it is true that the behavior is mandated by the JSF spec, then I am thinking the spec is wrong somehow (unless there's a good reason to swallow a runtime exception which I doubt there can be)... Perhaps there's a bug lurking somewhere... -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.jboss.com/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

[ https://jira.jboss.org/jira/browse/JBSEAM-2597?page=com.atlassian.jira.pl... ] Pete Muir closed JBSEAM-2597. ----------------------------- Resolution: Won't Fix This has to be solved by JSF, work is under way for JSF 2. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/jira/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira