DZone
Thanks for visiting DZone today,
Edit Profile
  • Manage Email Subscriptions
  • How to Post to DZone
  • Article Submission Guidelines
Sign Out View Profile
  • Post an Article
  • Manage My Drafts
Over 2 million developers have joined DZone.
Log In / Join
Refcards Trend Reports
Events Video Library
Refcards
Trend Reports

Events

View Events Video Library

Zones

Culture and Methodologies Agile Career Development Methodologies Team Management
Data Engineering AI/ML Big Data Data Databases IoT
Software Design and Architecture Cloud Architecture Containers Integration Microservices Performance Security
Coding Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks
Culture and Methodologies
Agile Career Development Methodologies Team Management
Data Engineering
AI/ML Big Data Data Databases IoT
Software Design and Architecture
Cloud Architecture Containers Integration Microservices Performance Security
Coding
Frameworks Java JavaScript Languages Tools
Testing, Deployment, and Maintenance
Deployment DevOps and CI/CD Maintenance Monitoring and Observability Testing, Tools, and Frameworks

How does AI transform chaos engineering from an experiment into a critical capability? Learn how to effectively operationalize the chaos.

Data quality isn't just a technical issue: It impacts an organization's compliance, operational efficiency, and customer satisfaction.

Are you a front-end or full-stack developer frustrated by front-end distractions? Learn to move forward with tooling and clear boundaries.

Developer Experience: Demand to support engineering teams has risen, and there is a shift from traditional DevOps to workflow improvements.

Related

  • Preventing Downtime in Public Safety Systems: DevOps Lessons from Production
  • How to Identify the Underlying Causes of Connection Timeout Errors for MongoDB With Java
  • Supercharge Your Java Apps With AI: A Practical Tutorial
  • Source-Driven Development in Salesforce: Managing Metadata and API Versions

Trending

  • DZone's Article Submission Guidelines
  • Beyond Java Streams: Exploring Alternative Functional Programming Approaches in Java
  • Mastering Kubernetes Observability: Boost Performance, Security, and Stability With Tracestore, OPA, Flagger, and Custom Metrics
  • AI Agent Architectures: Patterns, Applications, and Implementation Guide
  1. DZone
  2. Data Engineering
  3. Databases
  4. Propagate an Error Response in Mule API

Propagate an Error Response in Mule API

Read this tutorial that includes pictures for reference in order to learn more about how to propagate an error response in Mule API.

By 
Pranav Ladage user avatar
Pranav Ladage
·
May. 23, 18 · Tutorial
Likes (3)
Comment
Save
Tweet
Share
30.7K Views

Join the DZone community and get the full member experience.

Join For Free

Background

Mule API architecture suggests 3 layers of implementation i.e Experience layer, Process layer, and System layer.

What happens if an error occurs at System layer? You might have observed that whenever a system API throws an error (for example 404), the HTTP call in Process API goes into exception (org.mule.module.http.internal.request.ResponseValidatorException).

If you are using the generic apiKit Global Exception Mapping, it will be handled by 500 and your process API will return "500: Internal server Error: Response code 404 mapped as failure." Moreover, your Experience API will return "500: Internal Server Error: Response code 500 mapped as failure."

The client application that is consuming your experience API will have no clue of what went wrong with the response it received.

Requirement

We wish to propagate the response of system API to Experience API, so the client application consuming the experience API can figure out what exactly went wrong.

Solution

In the process API, the HTTP component that invokes the systems API, configure the "Target" as a flow variable.
Image title

In Exception handling Strategy, a catch exception strategy within a choice exception strategy can be used.

Image title

Set the Execute when: #[exception.causedBy(org.mule.module.http.internal.request.ResponseValidatorException)]

Image title

Set the property HTTP status by trimming the response message available.

Image title

Set the Payload with appropriate response data along with the flow variable saved.

Image title

Repeat the same with Experience API.

Conclusion

If data abstraction is not the requirement and we wish to propagate the error code from underlying APIs to client applications, this process can be used.

API

Opinions expressed by DZone contributors are their own.

Related

  • Preventing Downtime in Public Safety Systems: DevOps Lessons from Production
  • How to Identify the Underlying Causes of Connection Timeout Errors for MongoDB With Java
  • Supercharge Your Java Apps With AI: A Practical Tutorial
  • Source-Driven Development in Salesforce: Managing Metadata and API Versions

Partner Resources

×

Comments

The likes didn't load as expected. Please refresh the page and try again.

ABOUT US

  • About DZone
  • Support and feedback
  • Community research
  • Sitemap

ADVERTISE

  • Advertise with DZone

CONTRIBUTE ON DZONE

  • Article Submission Guidelines
  • Become a Contributor
  • Core Program
  • Visit the Writers' Zone

LEGAL

  • Terms of Service
  • Privacy Policy

CONTACT US

  • 3343 Perimeter Hill Drive
  • Suite 100
  • Nashville, TN 37211
  • [email protected]

Let's be friends: