[seam-issues] [JBoss JIRA] Commented: (SEAMREST-6) ExceptionMapper classes should be moved to api to support only relying on api jar at compile time

[Jozef Hartinger (JIRA)]

    [ https://jira.jboss.org/browse/SEAMREST-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12564012#comment-12564012 ] 

Jozef Hartinger commented on SEAMREST-6:
----------------------------------------

I understand what you mean. On the other hand, the ExceptionMappers represent the module logic and not an API that users should use (besides this single case). Anyway, the problem can be avoided by using JAX-RS scanning instead of explicitly selecting provider classes (simply do not override Application's classes)

> ExceptionMapper classes should be moved to api to support only relying on api jar at compile time
> -------------------------------------------------------------------------------------------------
>
>                 Key: SEAMREST-6
>                 URL: https://jira.jboss.org/browse/SEAMREST-6
>             Project: Seam REST
>          Issue Type: Bug
>          Components: Client
>    Affects Versions: Alpha1
>            Reporter: Jason Porter
>            Assignee: Jozef Hartinger
>
> Currently SeamExceptionMapper and ValidationExceptionMapper are in the impl class.  Unless we provide our own Application subclass (which should also be in the api jar) users can subclass and add to our classes they must include the impl jar as a runtime dependency.

-- 
This message is automatically generated by JIRA.
-
For more information on JIRA, see: http://www.atlassian.com/software/jira