Uploaded image for project: 'Seam REST'
  1. Seam REST
  2. SEAMREST-6

ExceptionMapper classes should be moved to api to support only relying on api jar at compile time

    Details

    • Type: Bug
    • Status: Open (View Workflow)
    • Priority: Major
    • Resolution: Unresolved
    • Affects Version/s: 3.0.0.Alpha1
    • Fix Version/s: Future
    • Component/s: Client
    • Labels:
      None
    • Steps to Reproduce:
      Hide

      Create a new application using seam rest and only have the API jar as compile scope, try to add the ExceptionMapper classes to a new application.

      Show
      Create a new application using seam rest and only have the API jar as compile scope, try to add the ExceptionMapper classes to a new application.
    • Affects:
      Interactive Demo/Tutorial, Compatibility/Configuration
    • Workaround:
      Workaround Exists
    • Workaround Description:
      Hide

      Use JAX-RS scanning instead of explicitly listing provider classes

      or

      Add the impl jar as compile scope

      Show
      Use JAX-RS scanning instead of explicitly listing provider classes or Add the impl jar as compile scope
    • Estimated Difficulty:
      Low

      Description

      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.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                Unassigned
                Reporter:
                lightguard Jason Porter
              • Votes:
                0 Vote for this issue
                Watchers:
                0 Start watching this issue

                Dates

                • Created:
                  Updated: