Uploaded image for project: 'Errai'
  1. Errai
  2. ERRAI-134

Provide a way to handle server-side exceptions on the client

    Details

    • Type: Enhancement
    • Status: Closed (View Workflow)
    • Priority: Major
    • Resolution: Done
    • Affects Version/s: 1.2
    • Fix Version/s: 1.3
    • Component/s: ErraiBus
    • Labels:
      None
    • Affects:
      Documentation (Ref Guide, User Guide, etc.), Release Notes, Interactive Demo/Tutorial
    • Estimated Difficulty:
      High

      Description

      Providing an ErrorCallback (using errorsHandledBy() in the MessageBuilder API) works fine for handling local exceptions but we also need support for handling remote exceptions that result from Errai RPC calls. Server-side exceptions are already sent to the client using a special message format but there they are only logged and reported to the user.

      A solution could be to internally create a temporary subscription to errors for a specific message and to invoke the corresponding client-side ErrorCallback from the MessageCallback.

      We also need to reconstruct (serialize/deserialize) the original Throwable to pass it to the error() method.

        Gliffy Diagrams

          Attachments

            Activity

              People

              • Assignee:
                csa Christian Sadilek
                Reporter:
                csa Christian Sadilek
              • Votes:
                0 Vote for this issue
                Watchers:
                1 Start watching this issue

                Dates

                • Created:
                  Updated:
                  Resolved: