DataWeaveELEMENTARY
Wrap System API Error as Problem Details Response
When a downstream System API call fails, the raw Mule error must never reach the API consumer unprocessed. This challenge places you inside an on-error-continue handler where you transform a Mule error object into a standardized Problem Details response. The upstream Inventory API is not always reachable — some failures return a structured HTTP error body, others return nothing at all — so you must guard every conditionally present field before the response goes out.
#error-handling#on-error-continue#rest-api
// Be first to rate this challenge!SCROLL TO READ ↓
The fastest way
to learn integration.
01.
Production payloads
Real CSV/JSON/XML you'll meet on day one — null fields, mixed casing, partial records.
02.
Design problems
What practitioners actually solve — null-safety, idempotency, retries, batch boundaries.
03.
Edge cases that break
Empty arrays, type coercion, deeply nested transforms, locale-specific dates.
…
CHALLENGES
…
MODULES
// Free forever · No credit card
Sign up.
Then code.
Free accounts get 3 attempts per challenge, full XP, and your trail progress synced across devices.
// WHAT YOU'LL BUILDHOW IT WORKS ↓
01.
Live DataWeave editor
Real DWL 2.0 IDE with helpers, modules, syntax highlighting.
02.
Test cases run on real runner
Same Go runner used in prod. Diffs show exactly which fields fail.
03.
3 graded attempts
Submit when you're ready. Score persists. Solution unlocks after pass or last attempt.
04.
Helpers & multi-module DWL
Bring in reusable %dw modules. Import, export, compose.
05.
XP & leaderboard
Points + XP awarded per challenge. Trail progress synced.
06.
Production-style payloads
Real CSV/JSON/XML — null fields, mixed casing, partial records.