Weave Code
Service Proxy Bundle Laravel Package
openclassrooms/service-proxy-bundle
A Symfony bundle for creating service proxies in the dependency injection container. It enables lazy initialization and method interception while preserving the original service API, helping defer expensive work without rewriting application code.
Service Proxy Symfony2 Bundle
Frequently asked questions about Service Proxy Bundle
- Can I install openclassrooms/service-proxy-bundle in a Laravel application with Composer?
- Practically no. The package is a Symfony 2 bundle that registers through AppKernel, a DependencyInjection Extension, and compiler passes, none of which exist in Laravel's container model. Its Composer constraints target the Symfony 2.0 to 2.8 line, which reached end of life in November 2018, so dependency resolution will almost certainly conflict with a modern PHP 8 and Laravel 8 to 11 stack. Forcing installation with --ignore-platform-reqs is a production anti-pattern, not a workaround.
- What does openclassrooms/service-proxy-bundle actually do?
- It is a Symfony 2 bundle for creating service proxies inside the dependency injection container. The proxies enable lazy initialization and method interception while preserving the original service API, so expensive work can be deferred without rewriting calling code. The exact proxy semantics, whether lazy loading, remote stubbing, or decorator-style interception, are coupled to Symfony's service definition lifecycle and should be confirmed by reading the source.
- Which Laravel and PHP versions does this package support?
- None officially. The bundle is built for Symfony 2.0 through 2.8 and the PHP versions of that era, roughly PHP 5.6 through 7.x, and no compatibility matrix was ever published. There is no Laravel support at all, since Laravel packages and Symfony bundles are structurally different artifacts. Always check composer.json before any evaluation rather than assuming it will resolve.
- Is openclassrooms/service-proxy-bundle still maintained?
- No. The repository shows a zero-star, zero-dependent profile and no release activity, which strongly suggests an internal OpenClassrooms utility that was published and abandoned. There is no issue triage, no security response process, and no upstream patch path. Verify the archived flag, last commit date, and license file yourself before spending any engineering time on it.
- What is the Laravel equivalent of this Symfony service proxy bundle?
- Laravel's service container bindings, deferred providers, and the HTTP client cover most of the same ground natively. For lazy resolution, bind a closure or use a deferred ServiceProvider; for remote service calls, wrap Http:: in a generated client interface; for interception, use decorators or middleware. Reach for ocramius/proxy-manager only if you genuinely need runtime virtual proxy generation.
- How hard is it to reimplement the proxy pattern natively in Laravel?
- For a bundle of this size and era, usually one to three days. A typical port is a ServiceProvider with contract bindings, an interface for the proxied service, and an HTTP client wrapper, backed by contract tests. Extract the pattern by reading the original source, classify it as lazy-loading, remote stub, or intercepting decorator, then map it onto the closest Laravel primitive. That is almost always cheaper than forking and maintaining an abandoned Symfony 2 dependency.
- Does this bundle work with Symfony 5, 6, or 7?
- No. It predates the Symfony Flex and bundle-less application structures and targets the Symfony 2.0 to 2.8 line that went end of life in November 2018 with extended support ending in 2019. Modern Symfony releases changed service definition handling and autowiring enough that the registration logic would need a rewrite. Treat the package as a design reference rather than something to install on any current framework.
- Is it safe to use this package in production or a commercial project?
- The technical risk is high. The upstream is abandoned, so any transitively pulled Symfony 2 packages with known CVEs have no patch path, test coverage is unknown, and there is no compatibility matrix or maintenance SLA. License ambiguity could also block commercial use if no clear license file exists. Audit the repository state first, and expect to own any fork you deploy.
- How do I migrate a Symfony bundle to a Laravel service provider?
- Map the bundle's DependencyInjection Extension to a ServiceProvider register and boot method, replace container service definitions with bindings and singletons, and convert compiler passes into explicit registration or config-driven wiring. Publish configuration with mergeConfigFrom and publish, and expose the API through contracts rather than a facade unless one is genuinely useful. Then write tests that assert the proxied behaviour matches the original.
- How should I test a proxied service in Laravel once I port it?
- Write contract tests that assert both pass-through behaviour and interception behaviour, so the proxy stays transparent to callers. Use container resolution tests to confirm the binding is lazy and only instantiates the real service on first use, and fake the underlying HTTP client for remote-backed proxies. Add a test that fails if the proxy changes the public API of the original service. These tests are cheap and are the main thing the abandoned bundle never guaranteed.
Weaver
How can I help you explore Laravel packages today?