[jbossseam-issues] [JBoss JIRA] Commented: (JBSEAM-2597) Exception handling - JSF swallows exceptions in certain phases

[asookazian (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...

> Exception handling - JSF swallows exceptions in certain phases
> --------------------------------------------------------------
>
>                 Key: JBSEAM-2597
>                 URL: http://jira.jboss.com/jira/browse/JBSEAM-2597
>             Project: Seam
>          Issue Type: Feature Request
>          Components: Exception Handling
>            Reporter: Shane Bryzak
>             Fix For: 2.1.0.BETA1
>
>
> I can't reproduce this right now but I'm sure I spent several hours
> with a debugger only to find out that I had a typo in a value binding
> and that the exception was completely swallowed during an early JSF
> phase (UPDATE MODEL probably). There was nothing in the log, the
> action phase just never executed. This is a major issue (obviously)
> for another subtle reason: Beginners have trouble understanding the
> JSF lifecycle and processing phases - I know I did. You begin to hate
> JSf when you don't understand why a certain phase does not execute.
> I'd start reproducing it by generating an NPE in a value binding
> setter, that should do it.

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