You are viewing a plain text version of this content. The canonical link for it is here.
Posted to users@tapestry.apache.org by Everton Agner <ev...@yahoo.com.br> on 2009/12/17 20:25:03 UTC
Exception Reporting and Production Mode configuration
Hi,
Maybe i misunderstood something about this... In AppModule class, When I have the PRODUCTION_MODE = "false", Tapestry should redirect to it's shiny Exception Reporting page (with info for the developer). So, when I have the PRODUCTION_MODE = "true", Tapestry should redirect to it's simplified version of the same Exception Reporting page OR redirect to my own implemented ExceptionReport page (user-friendly), if it exists.
Is that right?
I'm saying that because if I have my own implemented ExceptionReport page, the framework is always redirecting to it, no matter if the app is running on Production Mode or not...
Thanks!
Everton.
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
Re: Res: Exception Reporting and Production Mode configuration
Posted by Ulrich Stärk <ul...@spielviel.de>.
Better yet, make the contribution to the Alias service, where you
contribute your own ExceptionHandler, dependent on the value of the
production mode symbol.
Something along
public void contributeAlias(Configuration<AliasContribution>
configuration, MyOwnExceptionHandler handler, @Inject
@Symbol(SymbolConstants.PRODUCTION_MODE) boolean productionMode)
{
if (productionMode)
configuration.add(AliasContribution.create(MyOwnExceptionHandler.class,
handler));
}
Uli
Everton Agner schrieb:
> So, in development enviroment I need to delete the ExceptionReport page files to see the default Exception page?
>
>
>
>
> ________________________________
> De: Thiago H. de Paula Figueiredo <th...@gmail.com>
> Para: Tapestry users <us...@tapestry.apache.org>
> Enviadas: Quinta-feira, 17 de Dezembro de 2009 17:40:39
> Assunto: Re: Exception Reporting and Production Mode configuration
>
> Em Thu, 17 Dec 2009 17:25:03 -0200, Everton Agner <ev...@yahoo.com.br> escreveu:
>
>> Hi,
>
> Hi!
>
> Tapestry will always redirect to the configured exception page. The production mode symbol affects the Tapestry default erro page: if on, it shows almost nothing, otherwise, it shows all the information available.
>
>> I'm saying that because if I have my own implemented ExceptionReport page, the framework is always redirecting to it, no matter if the app is running on Production Mode or not...
>
> It's working as expected. :)
>
> --Thiago H. de Paula Figueiredo
> Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor
> Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda.
> http://www.arsmachina.com.br
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
> For additional commands, e-mail: users-help@tapestry.apache.org
>
>
> ____________________________________________________________________________________
> Veja quais são os assuntos do momento no Yahoo! +Buscados
> http://br.maisbuscados.yahoo.com
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
Res: Exception Reporting and Production Mode configuration
Posted by Everton Agner <ev...@yahoo.com.br>.
So, in development enviroment I need to delete the ExceptionReport page files to see the default Exception page?
________________________________
De: Thiago H. de Paula Figueiredo <th...@gmail.com>
Para: Tapestry users <us...@tapestry.apache.org>
Enviadas: Quinta-feira, 17 de Dezembro de 2009 17:40:39
Assunto: Re: Exception Reporting and Production Mode configuration
Em Thu, 17 Dec 2009 17:25:03 -0200, Everton Agner <ev...@yahoo.com.br> escreveu:
> Hi,
Hi!
Tapestry will always redirect to the configured exception page. The production mode symbol affects the Tapestry default erro page: if on, it shows almost nothing, otherwise, it shows all the information available.
> I'm saying that because if I have my own implemented ExceptionReport page, the framework is always redirecting to it, no matter if the app is running on Production Mode or not...
It's working as expected. :)
--Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer, and instructor
Owner, software architect and developer, Ars Machina Tecnologia da Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org
____________________________________________________________________________________
Veja quais são os assuntos do momento no Yahoo! +Buscados
http://br.maisbuscados.yahoo.com
Re: Exception Reporting and Production Mode configuration
Posted by "Thiago H. de Paula Figueiredo" <th...@gmail.com>.
Em Thu, 17 Dec 2009 17:25:03 -0200, Everton Agner
<ev...@yahoo.com.br> escreveu:
> Hi,
Hi!
Tapestry will always redirect to the configured exception page. The
production mode symbol affects the Tapestry default erro page: if on, it
shows almost nothing, otherwise, it shows all the information available.
> I'm saying that because if I have my own implemented ExceptionReport
> page, the framework is always redirecting to it, no matter if the app is
> running on Production Mode or not...
It's working as expected. :)
--
Thiago H. de Paula Figueiredo
Independent Java, Apache Tapestry 5 and Hibernate consultant, developer,
and instructor
Owner, software architect and developer, Ars Machina Tecnologia da
Informação Ltda.
http://www.arsmachina.com.br
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscribe@tapestry.apache.org
For additional commands, e-mail: users-help@tapestry.apache.org