Customizing Error Messages/Error Code in ADF BC Rest Web Services

Roshan Suntharan

Hi there,

We are looking for a way to customize error messages and codes in our ADF BC Rest webservices. Everything I've already looked at and been recommended shows implementing a custom error handler and setting it in DataBindings.cpx file and such. However, from all my research, it appears that this requires the uses of a UI to make this possible. Otherwise, this file is utterly useless. To be specific, we are using "ADF REST Web Application" projects, and not "ADF Fusion Web Application" - we are currently using both 12.2.1.3 and 12.2.1.4 weblogic (and JDeveloper) for our various clients.

Our application is purely webservice calls, no UI, and they typically get made from programs like Postman, ReadyAPI and such. Since most of our input validation, error checking, etc. is being done in our database (also an Oracle database), we want to be able to see what the error coming back is to adjust it and make it more user-friendly.

Also, as a result of 12.2.1.4 weblogic move, it appears the error message(s) are muted when the web service response is a 500. As a result, any issues that arise in the database come back to the webservice but we are unable to tell where the error occurred off the bat - we have to go into our logs which is time wasted.

If anyone can suggest a way to create custom error messages, and possibly even change the response code without the use of ADF BC UIs, that would be great. Thanks for everything.

Timo Hahn

https://community.oracle.com/tech/developers/discussion/4499670/customizing-error-messages-error-code-in-adf-bc-rest-web-services

The 'muted' error messages in case of a status 500 are a security measure. Otherwise, you could get information about the service you should not get by sending some bogus requests. For this, if you return status 500 you won't get any error info.

You can overwrite the entityImpl.doDML() method and put a try catch block around the super.doDML() call. If you get an exception you can e.g. send a validation exception. This should set the status to 400 and the error info is sent back automatically.

Timo

dvohra21

Custom error handler is the approach to take regardless of from where the error messages are coming.

Timo Hahn

https://community.oracle.com/tech/developers/discussion/4499670/customizing-error-messages-error-code-in-adf-bc-rest-web-services

The 'muted' error messages in case of a status 500 are a security measure. Otherwise, you could get information about the service you should not get by sending some bogus requests. For this, if you return status 500 you won't get any error info.

You can overwrite the entityImpl.doDML() method and put a try catch block around the super.doDML() call. If you get an exception you can e.g. send a validation exception. This should set the status to 400 and the error info is sent back automatically.

Timo

Roshan Suntharan

Hi Timo,

Thanks for taking the time to reply to this. That's exactly what we ended up implementing and it has resolved our issues.

Roshan