GlobalRemoteObjectFaultHandler Global Error Handler For Parsley 3

James Hill
James Hill
Published in
1 min readNov 7, 2016

Further to my previous post, I still couldn’t get the GlobalRemoteObjectFaultHandler Metadata tag to capture application exceptions being thrown globally. And the reason became perfectly clear upon studying the Cairngorm Parsley Integration code.

Seems the Cairngorm code base is still stuck pre-Parsley 3, almost a year and a half after it’s release.

Solution — Write the thing myself. Spent some time Googling for a solution, so I hope this might be useful to someone.

The functionality is encapsulated by two classes, and the extension initialised in a third. I’ve renamed the extension GlobalServiceFault — to keep a differentiation from the original. You can find the original ‘GlobalRemoteObjectFaultHandler’ code here.

And the ObjectProcessor …

To get it all working, you need to register the new Metadata with Parsley. (see here), and also specify to the mxmlc compiler to keep instances of your new metadata from being striped out.

--

--