ASDL Exit Type Not Set On Application Exception (Doc ID 441844.1)

Last updated on OCTOBER 12, 2016

Applies to:

Oracle Communications ASAP Cartridges - Version: 3.1.1 and later   [Release: Unknown Release and later ]

Symptoms

Work orders do not fail when errors occur; they simply succeed. Error handling in Provisioning.java source for "Application Exception" block catch conditions does not set ASDL exit type correctly. This has a major effect on user defined error code conditions. Example source extracted:

catch(AccessDenied ade) {
Diagnostic.diag(1, this, ""NOK-IN_J4-1--> "" + ade.strMessage + "", Host ""
+ ade.strHostName + "", Server "" + ade.strServerName + "", ErrorCode "" + ade.strNativeError);
super.uet = super.respHandler.checkNEResponse(ade.strNativeError);            setASDLExitType(super.uet.getUserExitType(), super.uet.getUserErrorText());
}
catch(ApplicationException ae){
Diagnostic.diag(1, this, ""NOK-IN_J4-1--> "" + ae.strMessage + "", Host "" + ae.strHostName + "", Server "" + ae.strServerName + "", ErrorCode "" + ae.strNativeError);
super.uet = super.respHandler.checkNEResponse(ae.strNativeError);       
}

Suggestion is to abstract an error class simplifying come removing some 42% of this source file.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms