Weave Code
Wsdl Laravel Package
php-soap/wsdl
php-soap/wsdl provides a modern PHP API for reading and navigating WSDL documents. Inspect services, bindings, ports, operations, and schemas, resolve imports, and power SOAP clients or code generation without manual XML parsing.
Deals with WSDLs
Frequently asked questions about Wsdl
- What is php-soap/wsdl used for?
- It parses WSDL 1.1 documents into a clean, typed object model so you can navigate definitions, services, ports, bindings, port types, operations, messages and parts without manual DOM traversal. It also exposes the embedded XML Schema types for inspection. Treat it as a parser primitive: useful for contract validation and diffing, code generation, service catalogs, and pre-flight checks before a SOAP call. It does not perform SOAP invocation itself.
- How do I install php-soap/wsdl in a Laravel application?
- Install it with Composer using composer require php-soap/wsdl. There is no service provider and no framework coupling, so you write a thin wrapper class, bind it to an interface in your own service provider, and decorate it with caching and an injected HTTP client. Keep the parsing work in queued jobs and artisan commands rather than in controllers.
- Is php-soap/wsdl a Laravel package or a SOAP client?
- Neither. It is a standalone, PHP-native WSDL parser with no Laravel dependency and no SOAP client or transport logic. The Laravel glue, caching, allowlisting and any actual request dispatching are yours to build, which keeps the library swappable but also means you own governance of the integration.
- Does php-soap/wsdl support WSDL 2.0?
- The documented feature set covers WSDL 1.1 with SOAP 1.1/1.2 and HTTP bindings. WSDL 2.0 support is not stated, so do not assume it works. Verify against your partner documents in a short spike before committing to the dependency if any of your contracts are WSDL 2.0.
- Does php-soap/wsdl resolve imported WSDL and XSD schemas?
- WSDL-level import resolution is part of the stated behaviour. Transitive XSD import/include handling, complex type resolution, choice/all groups and deeply nested includes are not spelled out, so test them explicitly. Run a spike against three real partner WSDLs, including one ugly legacy document with imports, before you depend on full schema fidelity.
- Is it safe to load remote WSDL URLs with php-soap/wsdl?
- Remote WSDL loading is both an SSRF and XXE surface if you wire it naively to user-supplied URLs. Confirm the parser disables external entity loading and entity expansion, and make sure you can inject your own HTTP client with a strict host allowlist. Where possible, pre-fetch WSDLs into storage and parse from disk instead of fetching at request time.
- Which PHP and Laravel versions does php-soap/wsdl support?
- It is a PHP-native Composer package, so Laravel version is largely irrelevant once your runtime PHP version satisfies the composer constraint. Check that constraint against your production runtime before adopting, and pin an explicit version. Because the project is pre-1.0, expect possible breaking changes under semver and plan upgrades deliberately.
- Can I cache or serialize the parsed WSDL object model?
- The typed object graph is a reasonable caching candidate, but confirm the model is stable enough to persist or serialize across releases first. If serialization proves fragile, cache the raw WSDL alongside a derived summary such as operations, endpoints and message shapes. Either way, wrap parsing in a cache decorator so repeated introspection does not re-parse on every request.
- How does php-soap/wsdl compare to ext-soap's built-in WSDL parsing?
- ext-soap bundles its own WSDL parser, but it is tied to the extension's engine and its dialect quirks, and it gives you little to navigate programmatically. php-soap/wsdl offers a modern typed object model built on php-soap/xml and fits the wider php-soap ecosystem. Pair it with a PSR-18 transport if you later need invocation, so you keep middleware, retries and observability. Validate against a fixture suite of real, sometimes non-conformant, partner documents rather than synthetic ones.
- Is php-soap/wsdl actively maintained and production ready?
- The project is small, with roughly 18 stars and an unverified repository, which signals a limited maintainer pool and real bus-factor exposure. Verify the release timeline and ask about the security disclosure process before production use, and pin or vendor the dependency. Have a fallback path, such as your own wrapper with a swappable parser implementation, so adoption risk stays contained.
Weaver
How can I help you explore Laravel packages today?