Uploaded image for project: 'Tapestry 5'
  1. Tapestry 5
  2. TAP5-198

Handling Exceptions in Components by replacing/returning another component

    XMLWordPrintableJSON

Details

    • Improvement
    • Status: Resolved
    • Minor
    • Resolution: Abandoned
    • 5.0.15
    • None
    • None
    • None

    Description

      When an exception occurs in a component, database/null pointer etc something that breaks the component, the exception propagates to the page and currently we show some error page.

      Unfortunately this breaks the whole page. I think it would be nice to have a way to define an error component to replace the one that brakes, so we lose only the component and not the whole page, something similar with have onException() and returning the error page.

      Currently we cant find a way to do that.

      Thanks,
      Sofoklis

      Attachments

        Activity

          People

            hlship Howard Lewis Ship
            sofoklis Sofoklis Papasofokli
            Votes:
            0 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

              Created:
              Updated:
              Resolved: