Have you looked at the link I've posted in my first message? :)
I know I can override the error page. But I like the default one. I just
don't like its default behavior which only relies on PRODUCTION_MODE
symbol.
What I suggest is to change this behavior and analyze if the user that get
this exce
On Fri, 27 Aug 2010 09:13:41 -0300, Dmitry Gusev
wrote:
Yes, I should say test.
I didn't mean running java debugger.
I mean trying to reproduce some test case using browser and getting
exception page.
You can override the error page (which I recommend, anyway), use the logic
you want for
Yes, I should say test.
I didn't mean running java debugger.
I mean trying to reproduce some test case using browser and getting
exception page.
On Fri, Aug 27, 2010 at 16:10, Thiago H. de Paula Figueiredo <
thiag...@gmail.com> wrote:
> On Fri, 27 Aug 2010 08:50:16 -0300, Dmitry Gusev
> wrote:
>
On Fri, 27 Aug 2010 08:50:16 -0300, Dmitry Gusev
wrote:
There might be another issue though, what if I need to debug application
behavior in production mode?
I can't think why you cannot debug the application in production mode in
the same way you do in non-production mode. Debugging is a
Thanks Jim, this might be a solution for most cases.
There might be another issue though, what if I need to debug application
behavior in production mode?
In this mode some services may work different way.
In this case there's no way to see detailed exception report on my
development machine.
But
Dmitry,
>From an example in an earlier post on this list, I use the approach of
having:
configuration.add(SymbolConstants.PRODUCTION_MODE, "true");
in my AppModule, so that by default production mode is always set to true
for deployments, and then for any run/debug configurations in the
develop
