Weave Code
Stomp Bundle Laravel Package
happyr/stomp-bundle
Symfony bundle that wraps the Stomp PHP client, adding configuration and service wiring for STOMP-compatible message brokers. It lets Symfony applications send messages to queues or topics on ActiveMQ, RabbitMQ, and similar messaging servers through a simple service.
A Symfony2 Bundle to wrap the fusesource/stomp-php library
Frequently asked questions about Stomp Bundle
- Can I install happyr/stomp-bundle in a Laravel application?
- No. It is a Symfony2 bundle that registers through Symfony's Bundle class and DependencyInjection extension, mechanisms Laravel's kernel never invokes. It has no Laravel service provider, facade, container binding, or config publish step, so nothing drops in. Its Composer constraints will very likely block installation on PHP 8.2+ and modern Laravel releases.
- Does happyr/stomp-bundle support Laravel 10 or Laravel 11?
- No. The package targets Symfony2-era applications, and Symfony 2.8 reached end-of-life in November 2018. Its Composer constraints very likely pin old Symfony and PHP versions, so installation on Laravel 10 or 11 is a non-starter. Read composer.json first; if it requires symfony/symfony ~2.x or PHP 5.x, the evaluation closes immediately.
- What does happyr/stomp-bundle actually do under the hood?
- It normalizes broker credentials from configuration, constructs a stomp-php client, registers that client as a Symfony container service, and exposes it for publishing messages. The Symfony plumbing is most of the package; the valuable logic is thin. Reimplementing the useful part in Laravel is roughly a small service provider plus a config file.
- How do I send STOMP messages to ActiveMQ or RabbitMQ from Laravel?
- If the broker supports AMQP, use a maintained Laravel queue driver and inherit retries, failed-job persistence, and monitoring for free. If the broker is STOMP-only, depend on the underlying stomp-php client directly and wrap it in a small Laravel service provider with an env-driven connection block. Do not port this bundle; rebuild only the credential normalization and client construction you actually need.
- Is happyr/stomp-bundle actively maintained?
- No. It has 1 star, 0 dependents, no release cadence, and no community surface for issue triage, security response, or PHP compatibility patches. Symfony 2.8 has been end-of-life since November 2018, and this wrapper has not followed later Symfony or PHP releases. Treat it as a dead artifact rather than a low-activity package.
- What are the risks of using an abandoned Symfony bundle for STOMP in Laravel?
- The main risk is abandonment, not code quality: no security response, no issue triage, and no PHP 8 compatibility patches. There is also transitive risk because the underlying stomp-php library has changed stewardship, and this wrapper has not followed it. The pairing is unverified against current broker versions, so you would own the adapter internally if upstream is gone.
- Should I use STOMP or AMQP for RabbitMQ in a Laravel app?
- If RabbitMQ is available through its AMQP adapter, this package and the surrounding STOMP discussion are irrelevant; use a maintained Laravel AMQP queue driver instead. STOMP is mainly justified when the target broker is genuinely STOMP-only, such as ActiveMQ Classic, Artemis, or HornetQ. For plain publish-and-consume workloads, a maintained transport gives higher operational leverage and a smaller custom surface.
- How much effort is porting happyr/stomp-bundle to Laravel?
- Expect roughly one to two engineering days, which is the honest cost floor for either porting or rebuilding. In Laravel terms, that means about a 150-line service provider, a config/stomp.php file, and an env-driven connection block around the underlying client. Because the bundle is thin, reimplementation beats porting, but adopting a maintained transport is usually the better default.
- Does happyr/stomp-bundle support STOMP receipts, transactions, or client acknowledgment modes?
- The bundle is a thin Symfony wrapper around stomp-php; it does not add notable STOMP semantics of its own beyond configuration and service wiring. If you need receipts, transactions, client or client-individual acknowledgment modes, or heartbeats, those behaviors come from the underlying client and broker. That requirement may justify a custom Laravel adapter, but not this abandoned bundle.
- What Laravel alternatives exist for STOMP messaging?
- Use a maintained Laravel queue driver when the broker speaks AMQP, such as an AMQP driver or laravel-queue-rabbitmq, so custom code drops to zero. For STOMP-only brokers, use the current stomp-php client directly behind a small Laravel service provider rather than this Symfony bundle. If STOMP-specific semantics are mandatory, budget for an internally owned adapter and confirm who maintains it.
Weaver
How can I help you explore Laravel packages today?