Ticket #2002 (closed defect: fixed)

Opened 3 months ago

Last modified 3 months ago

Component error handling

Reported by: Artur Signell Owned by: Artur Signell
Priority: undefined Milestone: User Interface Library 5.3.0 RC
Component: undefined Version: 5.2.5
Keywords: Cc:
Known Issue description:
Hours estimate: Deadline (dd.mm.yyyy):
Known Issue version (since): Known Issue title:
Hours done: Depends to:
Affects documentation: no
Known Issue workaround:
Affects release notes: no Contract:

Description

An application should be able to catch exceptions that happen in setValue (and other methods?) when processing data originating from the client (changeVariables()).

Change History

Changed 3 months ago by Jani Laakso

Please consider also #1642 as we do get "internal exceptions" in Toolkit that cannot be catched by Toolkit application any way. This is quite easy to fix, #1642 contains even crude solution example, so I suggest you give it a try.

Changed 3 months ago by Artur Signell

  • status changed from new to closed
  • resolution set to fixed

Added a component error handler to make it easier for a user to handle these kind of errors. Fixed changeVariables so an error in one component does not stop other components from being processed.

Changeset [5242]

Changed 3 months ago by Artur Signell

More generic implementation (AbstractComponent?) in [5250]. Reduced default logging to a minimum.

Note: See TracTickets for help on using tickets.