Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Minor Minor
    • Resolution: Invalid
    • Affects Version/s: 2.0
    • Fix Version/s: None
    • Component/s: None
    • Labels:
      None

      Description

      Since exceptions can be thrown from ContainerRequestFilter, do we need ContainerRequestContext.abortWith()? Instead the user can just throw an exception from the JAX-RS exception hierarchy to abort the request. Its pretty much the same thing, right, so I don't see an issue with removing abortWith().

        Activity

        Hide
        patriot1burke added a comment -

        Then again, abortWith() does make sense from a client perspective though:ClientRequestFilter and ClientRequestContext. In the client cache example, you certainly don't want an exception to propagate back up to application code when you abort the request with a cached entity. If you want symetry between client and server request filters, then maybe abortWith() has to stay.

        Show
        patriot1burke added a comment - Then again, abortWith() does make sense from a client perspective though:ClientRequestFilter and ClientRequestContext. In the client cache example, you certainly don't want an exception to propagate back up to application code when you abort the request with a cached entity. If you want symetry between client and server request filters, then maybe abortWith() has to stay.
        Hide
        patriot1burke added a comment -

        just a thought that wasn't received well. closing...

        Show
        patriot1burke added a comment - just a thought that wasn't received well. closing...

          People

          • Assignee:
            Unassigned
            Reporter:
            patriot1burke
          • Votes:
            0 Vote for this issue
            Watchers:
            0 Start watching this issue

            Dates

            • Created:
              Updated:
              Resolved: