[
https://jira.jboss.org/browse/SEAMCATCH-12?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12566650#comment-12566650
]
Dan Allen commented on SEAMCATCH-12:
------------------------------------
Perhaps we can leave off level in the first cut. I suggested it since it was
something that Seam 2's exception mapping config offered. But that was a
hard-coded behavior.
We also need to recommend how exception mappings are filtered by request type
(may just be a docs issue). It could be a qualifier that is added to the type
in the XML config (as opposed to a field on ExceptionResponse).
One of the key features of Seam Catch over the exception handling in Seam 2 is
that we are factoring into the design how to use different mappings for
different types of requests (or scenarios in general).
> Add ExceptionResponse to the API
> --------------------------------
>
> Key: SEAMCATCH-12
> URL: https://jira.jboss.org/browse/SEAMCATCH-12
> Project: Seam Catch
> Issue Type: Feature Request
> Affects Versions: Alpha1
> Reporter: Dan Allen
> Assignee: Jason Porter
> Priority: Minor
> Fix For: Alpha2
>
>
> Add a reusable ExceptionResponse value object to the API for use in
> specifying exception to HTTP responses. This will likely get reused by the
> JAX-RS, Servlet and JSF integrations, at the very least.
> ExceptionResponse {
> forType
> statusCode
> message
> logLevel?
> }
> A similar API was introduced in the REST module alpha. I'd like to
> consolidate such classes.
--
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
_______________________________________________
seam-issues mailing list
[email protected]
https://lists.jboss.org/mailman/listinfo/seam-issues
