Allow custom Exceptions to be public and referenced from other espaces

By Goncalo Borrega on 12 May 2010
Just as all other elements, the custom exception could be public so that on consumer espaces you can have error handling for specific custom exceptions of the producer espaces.

Showing what kind of exceptions are thrown in the tooltip of a user action would also be a good improvement
J.9 Jun 2010

I want this feature very much, because you want to bubble exceptions a through other espaces as well and handle them there accordingly.
Pedro Moreira4 Jun 2013
+1
Rogério Braudes14 Jan 2014
+1
André Ramos1 Sep 2011
It would be nice if we could define a user exception in one eSpace and use it across the factory without having to redfine them.

Merged from 'Allow user exceptions to be referenced between eSpaces' (idea created on 2011-09-01 15:52:56 by André Ramos), on 2014-01-24 13:26:05 by Gonçalo Borrêga
Igor Kirtak14 Aug 2014
+1
Justin James1 Sep 2014
I'd like for Exceptions to be public so they can be re-used. A few reasons:

1. We keep re-making the same exceptions over and over again.
2. Can handle exceptions from a Produce eSpace in a granular fashion in the Consumer eSpace.

J.Ja


Merged from 'Allow Exceptions to be public' (idea created on 2014-09-01 18:34:20 by Justin James), on 2014-09-23 23:26:46 by Gonçalo Borrêga
Daniel Martins2 Sep 2014
It would be definitely useful!

Merged from 'Allow Exceptions to be public' (idea created on 2014-09-01 18:34:20 by Justin James), on 2014-09-23 23:26:46 by Gonçalo Borrêga
J.2 Sep 2014
oh gawd, yes!



Merged from 'Allow Exceptions to be public' (idea created on 2014-09-01 18:34:20 by Justin James), on 2014-09-23 23:26:46 by Gonçalo Borrêga
Nuno Rolo3 Sep 2014
Nice idea.

Merged from 'Allow Exceptions to be public' (idea created on 2014-09-01 18:34:20 by Justin James), on 2014-09-23 23:26:46 by Gonçalo Borrêga
Patrícia Lopes22 Feb 2013
I found the need to handle message text shown in the various exceptions individually. Also there is no specific handler to timeout errors, for example.
So the idea was to have a centralized action where we could distinguish the type of exception that occurred in order to show different error text for each one.


Merged from 'Handle exception message individiually' (idea created on 2013-02-22 10:55:04 by Patrícia Lopes), on 2015-07-15 10:53:23 by Goncalo Borrega
Carlos Sousa20 Mar 2015
When referencing a module action I'dd like to map the user exceptions that module has in order to correcly trap them on my module.

At this point I can raise specific user exception on one module, but I can't trap them on the other module, since user exceptions are limited to the module scope.

I always have to use the exception message to distinguish them but this is not the most elegant solution. 


Merged from 'Mark an exception as pulbic' (idea created on 2015-03-20 15:53:43 by Carlos Sousa), on 2015-07-15 10:54:58 by Goncalo Borrega
Justin James22 Mar 2015
This should be merged with this one:

http://www.outsystems.com/ideas/100/allow-custom-exceptions-to-be-public-and-referenced-from-other-espaces

J.Ja


Merged from 'Mark an exception as pulbic' (idea created on 2015-03-20 15:53:43 by Carlos Sousa), on 2015-07-15 10:54:58 by Goncalo Borrega
You want to define exceptions where they occur - and you typically handle them somewhere else.
And you don't want all exceptions being catched with an "All exceptions" handler - in most programming languages using an "All exceptions handler" would be considered a blocking code style violations!

But without possibility to share exceptions between eSpaces, this is about the only choice... :-(

So would be very useful & much appreciated if this would be solved!

Jan-Hendrik
mariap15 Sep

+1