- How do I install mateusfbi/totvs-rm-soap in a Laravel application?
- Install it with Composer by pinning the 4.x line, for example composer require mateusfbi/totvs-rm-soap:^4.5.0. Confirm that PHP's SOAP extension is available in every environment, then publish any package configuration and verify the service provider bindings are registered. The assessment recommends validating against a sandbox or homologation endpoint before using production credentials.
- Which Laravel and PHP versions does this TOTVS RM SOAP package support?
- The provided assessment does not document a minimum PHP or Laravel version floor for the package. It notes that illuminate/* and phpdotenv appear only in require-dev, which suggests a thin runtime dependency surface confined to the framework itself. Check the package's composer.json constraints against your application before pinning ^4.5.0, and verify ext-soap availability across environments.
- Do I need to write SOAP XML envelopes manually when using this package?
- No. The package includes XML generators and a WebService layer so you can build and send requests to TOTVS RM web services without hand-writing XML envelopes or repeating boilerplate. This is the main reason to use it instead of calling SoapClient directly in each integration. You still need to understand the upstream service contracts and payload fields your RM operations require.
- What is the difference between transient and shared bindings in this package?
- The service provider exposes both transient and shared bindings, and the distinction is architecturally significant because it controls lifecycle and statefulness. Shared bindings are long-lived, while transient bindings are resolved fresh, so you must understand which services hold state in your use case. The assessment flags whether these semantics are documented for consumers as a key question, so review the provider and package docs before wiring them into application code.
- How does caching work for TOTVS RM SOAP requests in this package?
- The WebService layer includes caching alongside fail-fast behavior. The assessment specifically asks what the cache TTL and invalidation policy looks like and whether it is configurable per service, so treat caching as something to configure deliberately. Establish TTL and invalidation expectations before load and confirm how the cache behaves when an upstream SOAP call fails.
- Can I test this package without a live TOTVS RM endpoint?
- Yes. SoapClient is mocked in the package tests, so it is testable without network access, and the package ships its own PHPUnit bootstrap so it will not interfere with your host application's test harness. The release reports 57 tests and 158 assertions. The residual risk is at the untested boundary: real WSDL variation, authentication, and transport-level failures should be covered by an integration smoke test against a sandbox endpoint.
- What are the main production risks of integrating Laravel with TOTVS RM SOAP?
- The dominant external risk is schema drift in third-party WSDL contracts, and the dominant internal risk is XML generation bugs. This release mitigates some of that with fail-fast semantics, mocked SoapClient tests, and documentation covering services and troubleshooting. Roll out behind a feature flag, surface failures to callers as typed exceptions, and budget for periodic WSDL and schema review independent of package upgrades.
- Is ext-soap required for mateusfbi/totvs-rm-soap?
- SOAP integration requires PHP's SOAP extension, ext-soap. The assessment explicitly flags that ext-soap should be verified as a declared requirement, so check the package's composer.json and confirm the extension is enabled in local, CI, and production environments. Commands such as php -m or composer check-platform-reqs help catch missing extensions before deployment.
- Is this TOTVS RM SOAP package actively maintained?
- Quality signals are healthy: Pint and PHPStan run in CI, the release has 57 tests and 158 assertions, and Dependabot is enabled. Version 4.5.0 is a minor release with additive documentation and tests, so compatibility risk within the 4.x line is low. SOAP integrations still age with their upstream contracts, so budget for periodic WSDL review regardless of package upgrades.
- What should I check before rolling a TOTVS RM SOAP integration into production?
- Start with environment readiness: confirm ext-soap, the PHP and Laravel version floor, and network egress to the SOAP endpoints. Install and publish config, wire the service provider bindings, and confirm transient versus shared semantics for your use case. Stand up a sandbox smoke test using the documented happy paths, enable caching deliberately with agreed TTL and invalidation, then roll to production behind a feature flag with fail-fast errors surfaced as typed exceptions.