[ 
http://jira.magnolia-cms.com/browse/BLOSSOM-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Kimmo Björnsson updated BLOSSOM-41:
-----------------------------------

    Attachment: BlossomHandlerExceptionResolver.java

Attaching an updated version of the Resolver we use.

> Handler exceptions are not logged and Paragraph-rendering can fail silently - 
> should log which Page/Paragraph that fails
> ------------------------------------------------------------------------------------------------------------------------
>
>                 Key: BLOSSOM-41
>                 URL: http://jira.magnolia-cms.com/browse/BLOSSOM-41
>             Project: Magnolia Blossom Module
>          Issue Type: Improvement
>    Affects Versions: 1.2.1
>            Reporter: Kimmo Björnsson
>            Assignee: Tobias Mattsson
>             Fix For: 1.2.3
>
>         Attachments: BlossomHandlerExceptionResolver.java, 
> BlossomHandlerExceptionResolver.java
>
>
> If you don't specify an ExceptionResolver that logs Exceptions from 
> Controllers for example MissingServletRequestParameterException they fail 
> silently.
> If Blossom overrided protected processHandlerException in DispatcherServlet 
> and log which Page/Paragraph that fails that would improve bug-searching a 
> lot in both cases (when the exception gets logged and when it doesn't).
> Or a BlossomHandlerExceptionResolver could be implemented that logs more 
> magnolia-specific info.
> I attached my BlossomHandlerExceptionResolver i created to log JCR-path to 
> help me find my bugs.

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: 
http://jira.magnolia-cms.com/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira




----------------------------------------------------------------
For list details see
http://www.magnolia-cms.com/home/community/mailing-lists.html
To unsubscribe, E-mail to: <dev-list-unsubscr...@magnolia-cms.com>
----------------------------------------------------------------

Reply via email to