myfaces-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Pavitra Subramaniam (JIRA)" <>
Subject [jira] Commented: (TRINIDAD-2038) Need new exception to know whether JSF needs to report the exception
Date Wed, 16 Feb 2011 20:35:24 GMT


Pavitra Subramaniam commented on TRINIDAD-2038:

Hello Hongbing, 

You mentioned that exceptions get thrown by model layer outside of JSF. Can you give an e.g.,
of when this might occur? 
How exactly will the above interface get used?


> Need new exception to know whether JSF needs to report the exception
> --------------------------------------------------------------------
>                 Key: TRINIDAD-2038
>                 URL:
>             Project: MyFaces Trinidad
>          Issue Type: Bug
>    Affects Versions: 2.0.0-beta-1
>            Reporter: hongbing wang
> There are cases that exception is thrown in update model phase, like model layer validation
failure, by model outside of JSF and the exception is also handled and reported outside of
JSF. To avoid the component's local value getting reset to null, JSF needs to be notified
when the it happens. The proposed solution is to re-throw a special exception to JSF and also
let JSF to know whether it needs to report the exception.
> Here is the interface of the exception:
> package org.apache.myfaces.trinidad.context;
> /**
>  * Interface for exceptions that tells whether the exception needs to be reported.
>  * If an exception is thrown during JSF lifycycle and aleady reported, then it should
>  * JSF know not to report it again.
>  *
>  */
> public interface Reportable
> {
>   /**
>    * Return false if JSF doesn't need to report this exception, otherwise true.
>    */
>   public boolean isReportingMessage();
> }  

This message is automatically generated by JIRA.
For more information on JIRA, see:


View raw message