Weave Code
Soap Process Bundle Laravel Package
cleverage/soap-process-bundle
CleverAge/SoapProcessBundle adds SOAP integration to the CleverAge ProcessBundle, helping Symfony applications configure and run SOAP-based process tasks. Part of CleverAge’s process tooling, MIT licensed, with usage docs included.
CleverAge/SoapProcessBundle brings SOAP integration to the CleverAge/ProcessBundle ecosystem. It lets you plug SOAP-based services into your processing pipelines, so remote web services can be called and handled alongside your other process steps in a consistent, bundle-driven way. It supports current Symfony stable releases and the latest LTS version.
- Seamless SOAP integration with ProcessBundle workflows
- Works with supported Symfony stable and LTS releases
- Clean, bundle-based configuration
- Part of the broader CleverAge ProcessBundle project
- Open source under the MIT license
See docs/index.md for usage documentation.
Frequently asked questions about Soap Process Bundle
- What is cleverage/soap-process-bundle used for?
- It is a Symfony bundle that provides SOAP integration for the CleverAge ProcessBundle v3. It abstracts SOAP service calls, WSDL handling, envelopes, and fault handling inside process workflows. Laravel teams typically evaluate it as a Symfony-compatible dependency or wrap it in a Laravel package.
- How do I install cleverage/soap-process-bundle with Composer?
- Install it with Composer using the package name cleverage/soap-process-bundle. First audit your composer.json for PHP and Symfony version constraints, because v3.0 targets modern PHP and Symfony releases. In Laravel, expect to add manual bundle registration or a custom wrapper rather than relying on a native Laravel service provider.
- Is cleverage/soap-process-bundle compatible with Laravel?
- It is Symfony-based and does not ship a native Laravel service provider or Facade. Laravel integration is possible through Symfony components, a custom wrapper package, or direct use of the bundle classes in your application services. You should verify version alignment and avoid conflicts with Laravel HTTP client handling.
- Which PHP and Symfony versions does soap-process-bundle require?
- The v3.0 release aligns with PHP 8.5 and Symfony 8 according to the technical evaluation. Projects still on PHP 8.1 or Symfony 7.3 face a higher risk of breaking changes and may need to upgrade or fork. Always confirm the exact constraints in composer.json before upgrading.
- How do I configure SOAP endpoints with cleverage/soap-process-bundle?
- The bundle integrates SOAP services into ProcessBundle workflows, so endpoint configuration is typically handled through Symfony bundle configuration and process definitions. It aims to reduce boilerplate for WSDL parsing, SOAP envelopes, and fault handling. For Laravel, bind the relevant configuration or wrap the bundle classes in your own service layer, and consult docs/index.md for usage details.
- Can I use cleverage/soap-process-bundle in a Laravel service provider?
- There is no native Laravel service provider, but you can create a custom Laravel provider or wrapper to register the bundle classes and expose facades if needed. Another option is injecting SoapClient or SoapProcess abstractions directly into App\Services classes. Be careful not to duplicate SOAP handling with Laravel's HTTP client.
- How do I test SOAP integrations using soap-process-bundle?
- Mock SOAP endpoints in CI and validate WSDL and XML schemas before integration testing. Test early against PHP 8.5 and Symfony 8 if that is your target stack. Bundle changes can expose SOAP-specific edge cases such as namespaces, encoding, and fault responses.
- What are alternatives to cleverage/soap-process-bundle for Laravel SOAP?
- Common alternatives include the native php-soap extension, guzzle-soap, diabol/soap, or custom SOAP handling with Symfony HttpClient. Choose based on WSDL support, Laravel integration needs, and maintenance activity. The bundle is most relevant when you already use CleverAge ProcessBundle workflows.
- Is cleverage/soap-process-bundle production-ready for high-volume SOAP requests?
- Production suitability depends on your SOAP workflow and how you integrate the Symfony bundle into Laravel. Benchmark it against native php-soap or Guzzle for high-volume request patterns and validate fault handling and schema validation. Because SOAP is verbose, pre-validate request and response schemas to reduce runtime errors.
- What breaking changes or maintenance concerns affect soap-process-bundle v3?
- Version 3.0 targets PHP 8.5 and Symfony 8, so older PHP 8.1 or Symfony 7.3 projects must upgrade or fork the package. The lack of a native Laravel provider means any Laravel wrapper you build needs ongoing maintenance. Check the bundle roadmap against Symfony LTS support and your own Laravel upgrade cycle.
Weaver
How can I help you explore Laravel packages today?