wsdltophp / domhandler

Decorative design pattern to ease DOM handling

WsdlToPhp

WsdlToPhp

This project aims to provide multiple components that eases the use of SOAP oriented Web Services.

To do this, the first component if the Package Generator.

The package generator

This component as it is named provides an easy way to generate a PHP package.

The generated package then provides all the methods to send any request to any operation provided by the Web Service.

You can find this component under src/WsdlToPhp/PackageGenerator directory.

The php generator

This component as it is named provides an easy way to generate a PHP source code.

This component is used by the package generator to ensure stability and consistency among generated PHP files.

You can find this component under src/WsdlToPhp/PhpGenerator directory.

The package base classes

This component as it is named provides base classes for the classes generated by the package generator.

This component is used by the package generator and as a dependency for the generated package.

You can find this component under src/WsdlToPhp/PackageBase directory.

The bundle generator

The bundle generator will aim to provide an easy way to generate a symfony bundle based on the generated package.

The generated bundle then provides services and other things to use the generated package as a symfony bundle.

This component will be available under src/WsdlToPhp/BundleGenerator directory.

Roadmap

First step: finalize package generator refactoring

As you must know, the package generator is based on the original project WsdlToPhp with a more robust and extensible way.

Nevertheless, it still remains some code parts that are not optimal and require refactoring.

This step will be developed under the feature/mandevilla branch.

Second step: optimize what can be optimized

In order to be able to provide a real interesting bundle generation experience, it's essential to be sure that the package generator is as fast as possible.

This step will be developed under the feature/anthurium branch.

Third step: create the bundle generator

As soon as the package generator is really finished, this generator will be developped under the feature/orchid.

domhandler's Issues

getAttributes returns an empty array

Having an element such as:

<xsd:element minOccurs="0" maxOccurs="1" name="Version" type="xsd:string" default="2.2" />

And having loaded this element using the ElementHandler class.

When calling the getAttributes, an array containing the element attributes (minOccurs, maxOccurs, name, type and default) should be returned whereas it is currently an empty array that is returned.

DOMXPath::query(): Node From Wrong Document

When using getElementsByNameAndAttributes with the $node parameter defined, if the $node is not contained by the DOMDocument contained by the current element on which the getElementsByNameAndAttributes is called, the error DOMXPath::query(): Node From Wrong Document is throwned