Weave Code
Doctrine Process Bundle Laravel Package
cleverage/doctrine-process-bundle
Integrates Doctrine with the CleverAge ProcessBundle, letting you use Doctrine entities and repositories within your process workflows. Part of the CleverAge ProcessBundle project for Symfony.
CleverAge/DoctrineProcessBundle integrates the Doctrine library into the CleverAge/ProcessBundle ecosystem, letting you build process workflows that read from and write to database entities. It is compatible with Symfony stable and LTS releases.
- Doctrine integration for ProcessBundle workflows
- Read/write entities as process data sources and targets
- Works with Symfony stable and LTS versions
- Part of the CleverAge ProcessBundle suite
- MIT licensed and open source
Frequently asked questions about Doctrine Process Bundle
- What is cleverage/doctrine-process-bundle used for?
- It is a Symfony bundle that integrates Doctrine ORM and DBAL into CleverAge ProcessBundle workflows. It lets process tasks read from and write to Doctrine entities or database tables and manage the entity manager during long-running pipelines. It is not an Eloquent or Laravel package.
- Can I use cleverage/doctrine-process-bundle in a Laravel application?
- No, it has no Laravel service provider, facade, config publishing, or Eloquent integration. It depends on a Symfony kernel and DI extension lifecycle, and Doctrine ORM bridges for Laravel do not register Symfony bundles. The practical options are a Symfony sidecar service or reusing the ProcessBundle workflow pattern in Laravel-native code.
- How do I install cleverage/doctrine-process-bundle?
- Install it with Composer alongside CleverAge ProcessBundle and DoctrineBundle, then register the bundle in your Symfony application. Configure services under the cleverage_doctrine_process alias and tag task services according to ProcessBundle conventions. This is Symfony bundle setup, not Laravel package installation.
- Which Symfony and PHP versions does cleverage/doctrine-process-bundle support?
- The README states compatibility with Symfony stable and the latest LTS release. v3.0 adds PHP 8.5 and Symfony 8 support while dropping PHP 8.1 and Symfony 7.3. Confirm the exact matrix for your platform before locking versions, because it is a bleeding-edge set.
- Which Doctrine versions does cleverage/doctrine-process-bundle require?
- It requires doctrine/orm ^2.9 || ^3.0 and doctrine/dbal ^2.9 || ^3.0, with DBAL 4 explicitly forbidden. It also depends on doctrine/doctrine-bundle ^2.5, doctrine/common ^3.0, doctrine/doctrine-migrations-bundle ^3.2, and ProcessBundle ^5.0. Check the release you install because this matrix is tight.
- What tasks does the bundle provide for process workflows?
- It provides DoctrineReaderTask, DatabaseReaderTask, DoctrineWriterTask, DoctrineRemoverTask, DoctrineDetacherTask, DoctrineRefresherTask, ClearEntityManagerTask, and DatabaseUpdaterTask. These tasks read from and write to Doctrine entities or database tables inside a ProcessBundle workflow. You can also clear the entity manager as an explicit workflow step.
- Does cleverage/doctrine-process-bundle support autowiring or automatic task discovery?
- The bundle registers services through a Symfony DI extension with the cleverage_doctrine_process alias, and v2.0 deliberately disabled autowiring and autoconfiguration. Task discovery relies on Symfony tagged-service conventions, so you must tag and configure task services explicitly. Do not expect Laravel-style package discovery.
- How should I test a Doctrine ProcessBundle workflow?
- Test in a Symfony kernel with a dedicated test database and Doctrine schema or migrations. Wrap each scenario in transactions and roll back where possible, and explicitly test entity manager clearing and resumability. There is no Laravel RefreshDatabase trait for this bundle.
- Is cleverage/doctrine-process-bundle safe for production and actively maintained?
- Package health signals are weak: zero stars, zero dependents, single-vendor CleverAge maintenance, and GitHub-issues-only support. Major versions shipped BC breaks, and DoctrineWriterTask global_flush was removed because ORM 3 removed partial-flush semantics. v3.2 fixed correctness defects, but the 2026-10-23 release date looks anomalous, so verify it before planning. Treat production adoption as a vendor-spike decision.
- What are alternatives to cleverage/doctrine-process-bundle for Laravel?
- For Laravel, use native queues, job batching, and Eloquent state tables rather than this Symfony bundle. If you need the ProcessBundle model, run it in a Symfony sidecar or evaluate standalone ProcessBundle service wiring. Other PHP workflow or pipeline packages may fit better than bridging Doctrine bundles into Laravel.
Weaver
How can I help you explore Laravel packages today?