When creating a shared library, what should the common logic application's pom.xml packaging type be?

• A. mule-plugin
• B. mule-application
• C. mule-domain
• D. mule-service

Answer: (D)

When you want a reusable set of logic that multiple apps can use, you package it as a Mule Service. Packaging as a mule-service tells the Maven/Mule runtime that this artifact is a deployable library, not a standalone application or a domain, but a service that provides shared flows, processors, or components that other apps can reference at runtime. This makes the artifact available to other applications by deploying it to the runtime and importing or depending on it as a shared resource.

Packaging as mule-application would imply a standalone Mule app, mule-domain is for resources shared at the domain level, and mule-plugin is for building connectors or extensions. Therefore, the shared library should be packaged as a mule-service.