add new issue       

Issue ID:  679     Enable changing of server exception before generation of DataPortalException from server      
Created by rocky on 2010-01-05 12:08 PM, 2876 days ago
Project:  CSLA .NET
Category:  enhancement
Priority:  med
Status:  closed
Feature area:Data Portal
Version:4.0.x
  Entering "issue#999" in comment creates link to id 999

show inline images      show change history

comment 2593 posted by JonnyBee on 2010-06-03 6:30 AM, 2727 days ago 
Altered how Server\xyzDataPortal transforms Exception to DataPortalExceptionHandler
Isolated exception handling into one class, DataPortalExceptionManager
DPEM provides a property and config entry for custom IDataPortalExceptionInspector class
Added GenericBusinessException to hold info about non-serializable or non-existing exception on client

The SL dataportal already handles this by custom WcfErrorInfo to hold Exception info.
comment 2305 posted by rocky on 2010-03-24 9:55 PM, 2798 days ago 
Possibly just mark the exception parameter to DataPortal_Exception as a 'ref' parameter.

A similar change would be required for object factories as well.
comment 1975 posted by rocky on 2010-01-05 12:08 PM, 2876 days ago 
Add an ExceptionHandler hook to serverside DataPortal.
I have run into problems when using f.ex IBM MQ or TeraData .Net driver when
a "non-standard" Exception (like MqException og TdException) is thrown but
these assemblies (drivers)  does not exist on the client and causes an a new
SerializationException on the client as Csla tries to deserialize the
DataPortal Exception. I'd like to hook into the serverside DataPortal -
inspect the Exception type, ad maybe log the actual exception and rethrow a
new known Exception type that the client can deserialize.