This might help you further.
http://jumpstart.doublenegative.com.au/jumpstart7/examples/infrastructure/exceptionreport
Cheers,
Geoff
On 24 Oct 2014, at 2:30 pm, Deepak <mn.dee...@gmail.com> wrote:
> Thanks a lot for the pointer. With the setting of tapestry.production-mode
> the stack trace is now displayed in its full glory :)
>
> On Fri, Oct 24, 2014 at 1:02 AM, Thiago H de Paula Figueiredo <
> thiag...@gmail.com> wrote:
>
>> On Thu, 23 Oct 2014 17:01:42 -0200, Deepak <mn.dee...@gmail.com> wrote:
>>
>> Hi, Thiago.
>>
>>
>> Hi!
>>
>> No, I've not created log4j.properties file but I've set the app to run in
>> development mode under web.xml as
>>
>> <context-param>
>> <param-name>tapestry.execution-mode</param-name>
>> <param-value>development</param-value>
>> </context-param>
>>
>>
>> This just tells DevelopmentModule to be loaded alongside AppModule, not
>> setting the production mode. You need to set the tapestry.production-mode
>> symbol to false.
>>
>> I've attached the screen shot of how exception is displayed in the app.
>>
>>
>> I'm sorry, but the screenshot wasn't actually attached. In addition,
>> please post the stack trace as text.
>>
>> --
>> Thiago H. de Paula Figueiredo
>> Tapestry, Java and Hibernate consultant and developer
>> http://machina.com.br
>>
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@tapestry.apache.org
For additional commands, e-mail: users-h...@tapestry.apache.org
