Doctrine Xinclude Xml Driver Bundle Laravel Package

Product Decisions This Supports

• Stack-fit validation: This is a Symfony bundle for Doctrine’s XML mapping driver, not a Laravel-native package. It is relevant only if the product is built on Symfony + Doctrine and deliberately uses XML mappings.
• Modular domain mapping: XInclude support lets teams compose Doctrine XML mapping files from smaller XML fragments. This supports bounded-context ownership, plugin/module mapping, and reducing merge conflicts in large domain models.
• Build vs. buy: Treat this as a vendor/fork candidate, not a strategic buy. The code surface is likely small, MIT-licensed, and easy to copy, but the package has weak adoption signals: 1 star, 0 dependents, last release February 2023.
• Roadmap gating: Use it only for a time-boxed spike or internal modularization effort. Do not put it on the critical path for a new product without an ADR, dependency review, and fallback plan.
• Laravel decision: For Laravel/Eloquent products, reject as a direct dependency. If Laravel is using Doctrine through an extension, this Symfony bundle is still not a drop-in fit because of its Symfony bundle integration.
• Use-case fit: Strongest fit is a Symfony/Doctrine application with multiple teams or modules shipping XML mapping fragments that must be composed without a single monolithic mapping file.

When to Consider This Package

• You are maintaining a Symfony application using Doctrine ORM/ODM XML mapping.
• You specifically need xi:include-style composition of Doctrine mapping files across modules, packages, or bounded contexts.
• You can pin Symfony, Doctrine, and PHP versions and accept that the package may need patching or forking.
• You are willing to vendor the code under MIT and assign internal ownership.
• The scope is small, reversible, and validated by a spike with representative mapping files.

Look elsewhere when:

• The product uses Laravel/Eloquent, or Doctrine mappings are defined via attributes, PHP, or YAML.
• You need active maintenance, security responsiveness, broad community support, or a proven dependency with real-world dependents.
• The mapping composition need can be solved with a small in-house XML preprocessor or by consolidating mappings into PHP/attribute-based configuration.
• The use case is production-critical and the team cannot own a fork.

How to Pitch It (Stakeholders)

For executives: This is a small, MIT-licensed Symfony/Doctrine utility that could help modularize XML mapping files using XInclude. It is not a strategic platform dependency: adoption is effectively zero, the last release was in 2023, and it has no dependents. Approve only a low-cost, time-boxed evaluation if the product already uses Symfony + Doctrine XML mappings; otherwise do not fund adoption.

For engineering: The bundle adds XInclude support to Doctrine’s XML mapping driver. It may be useful for composing mapping fragments across modules, but expect to vendor or fork it. Validate compatibility with the current Symfony/Doctrine/PHP matrix, add regression tests around mapping loads, and document an exit path. For Laravel or attribute/YAML-based Doctrine setups, do not integrate it directly.