Exception mapping using api kit
0 likes255 views
This document discusses exception mapping using APIKit in Mule. It explains that exception mapping provides a way to throw exceptions from an API in a RESTful way by specifying a status code, response message, and content type. The structure of an exception mapping declares these attributes. Exception mappings can also be auto-generated or custom mappings can be created by determining the exception, status code, and message.
1 of 6
Download to read offline
More Related Content
Ad
Similar to Exception mapping using api kit (20)
Ad
More from fedefortin (6)
Exception mapping using api kit
- 2. What is the exception mapping? - If you are creating an API using Mule, there will be times when you have to throw an exception. If you want to provide a better comment of what is going on inside of your code, you should explain it in a REST way, using an status code, a response comment and the content type of it. This is when the exception mapping comes handy.
- 3. Structure Each exception mapping is declared with the following attributes: Status code <apikit:mapping statusCode="400"> Used to indicate the status number. Exception value: <apikit:exception value="org.mule.module.apikit.exception.BadRequestException" /> Used to indicate the exception that will call this mapping. Content-Type: <set-property propertyName="Content-Type" value="application/json" doc:name=" Property" /> Used to indicate the content - type of the payload Payload: <set-payload value="{ "message": "Bad request" }" doc:name="Set Payload" /> Used to indicate the message of the error.
- 5. Creating your own mapping - Determine which exception will produce the error - The exceptions can only be declared once in the exception mapping - Choose the status code and message of the error. - Optionally, you can add the content-type of the error message.