Fixing XSLT Import Issues in MuleSoft Introduction 🔹 Scenario 🔹 Local Setup vs Runtime Issue In the General section, I used: • Inside the parent XSL, I imported the child XSL using: 📸 (Refer to the screenshot above for the exact configuration) 👉 With this setup, the transformation worked perfectly in the local environment (Anypoint Studio). 🔴 Issue in Runtime Fabric (RTF) However, when the same application was deployed to the RTF (Runtime Fabric) environment, the transformation failed with the following error: [2026-04-21 17:50:36.966] ERROR DefaultExceptionListener [[MuleRuntime].uber.03: [test].test.CPU_INTENSIVE @65f712f4] [event: ]: Message : I/O error reported by XML parser processing file:/apps/test/xslt/xsl/child.xsl: /apps/test/xslt/xsl/child.xsl (No such file or directory) 💡 Why This Happens In Anypoint Studio (local): In RTF (runtime): 👉 That’s why the child XSL cannot be found in runtime 🔴 Failed Approaches Using classpath inside parent XSL Message : I/O error reported by XML parser processing classpath:/xslt.xsl/child.xsl: unknown protocol: classpath Using relative path Message : I/O error reported by XML parser processing file:/tmp/child.xsl: /tmp/child.xsl (No such file or directory) Using absolute path Message : I/O error reported by XML parser processing file:/xslt/child.xsl: /xslt/child.xsl (No such file or directory) ✅ Final Working Solution xml-module:xslt /xml-module:xslt ✔ Step 2: Use classpath inside parent XSL ✔ Step 3: Ensure correct folder structure ✔ Step 4: Match Mule XML Module dependency with runtime 👉 Important: Dependency version must align with your Mule runtime. 💡 Bonus Insight 🔹 Conclusion ✍️ Author https://www.linkedin.com/in/sphurthi-edara/