Replies: 2 comments 8 replies
|
Hi @gigerIT Http binding is currently not supported. Wsdl1 with Soap 1.1 or soap 1.2 bindings are supported. |
|
I was able to generate it with v3 of this package and the same wsdl. What changed that it's now failing with v4? |
|
Thank you very much for taking time to look into this. I was able to successfully generate everything in v4, using php-soap/wsdl-reader#43 and commented out I'm now trying to figure out how I can set the API endpoint in my new ClientFactory. $engine = DefaultEngineFactory::create(
ExtSoapOptions::defaults(self::WSDL, [
'location' => $endpoint, // <-- SET LOCATION
'typemap' => new TypeConverterCollection([
new DateTimeTypeConverter(),
new TypeConverter\DateTypeConverter(),
new TypeConverter\DecimalTypeConverter(),
new TypeConverter\DoubleTypeConverter()
]),
]
)->disableWsdlCache()->withClassMap(FerrygatewayClassmap::getCollection()),But that seems not to be a thing anymore with the v4 EngineOptions. |
|
Hello, https://docs.php-http.org/en/latest/plugins/request-uri-manipulations.html |
|
It worked perfectly, thank you again! (Another step closer 🤞). Now, another peculiarity of this API is causing issues (I pretty much expected this to happen). To handle this, I wrote a middleware that strips away the SOAP envelope, etc., from the message just before sending the request, then re-adds it to the response before processing. <?php
namespace Ferrygateway\Middleware;
use Ferrygateway\FerrygatewayClient;
use Http\Client\Common\Plugin;
use Http\Promise\Promise;
use Psr\Http\Message\RequestInterface;
use Psr\Http\Message\ResponseInterface;
use Soap\Psr18Transport\Xml\XmlMessageManipulator;
use Soap\Xml\Locator\SoapBodyLocator;
use VeeWee\Xml\Dom\Document;
use function VeeWee\Xml\Encoding\element_encode;
class SoapToRestXmlMiddleware implements Plugin
{
public $originalRequestDocument;
/**
* converts a SOAP request to a FGW REST request
* @param RequestInterface $request
* @param callable $next
* @param callable $first
* @return Promise
* @throws \VeeWee\Xml\Encoding\Exception\EncodingException
*/
public function handleRequest(RequestInterface $request, callable $next, callable $first): Promise
{
$request = (new XmlMessageManipulator)(
$request,
function (Document $document) use ($request) {
//$rawXml = $document->toXmlString();
$this->originalRequestDocument = &$document;
$bodyElement = $document->locate(new SoapBodyLocator());
//$bodyXml = $bodyElement->toXmlString();
$requestElement = $bodyElement->firstElementChild->firstElementChild;
$requestElement->setAttribute('xmlns', 'http://schemas.ferrygateway.org/1.3.1');
$requestElement->removeAttribute('xsi:type');
foreach ($requestElement->getElementsByTagName('*') as $element) {
$element->removeAttribute('xsi:type');
}
$requestElement->getElementsByTagName('Context')->item(0)->setAttribute('TimeStamp', date('Y-m-d\TH:i:s'));
$document->manipulate(function (\DOMDocument $domDocument) use ($requestElement) {
//clear the whole dom document
foreach ($domDocument->getElementsByTagName('*') as $element) {
$domDocument->removeChild($element);
}
//attach the new cleaned request element
$domDocument->append($requestElement);
});
$xmlFinal = $document->toXmlString();
global $log;
if($log){
$log->request(
$xmlFinal,
api: FerrygatewayClient::API,
type: $requestElement->tagName,
method: $request->getMethod(),
url: $request->getUri(),
headers: $request->getHeaders(),
);
}
return $document;
}
);
/** Converts a FGW REST XML response to a SOAP response in order to parse the data by the SOAP package */
return $next($request)->then(function (ResponseInterface $response): ResponseInterface {
return (new XmlMessageManipulator)(
$response,
fn(Document $document) => $document->manipulate(
function (\DOMDocument $domDocument) use ($response) {
$decoded = \VeeWee\Xml\Encoding\element_decode($domDocument->documentElement);
$responseName = array_key_first($decoded);
global $log;
if($log){
$log->response(
$domDocument->saveXML(),
headers: $response->getHeaders(),
statusCode: $response->getStatusCode(),
);
}
$decoded[$responseName]['@attributes']['xsi:type'] = "fgw:" . $responseName . 'Type';
//attach "attributes" to all top level elements
foreach ($decoded[$responseName] as $elementName => $element) {
if (in_array($elementName, ['@namespaces', '@attributes', '@value'])) {
continue;
}
if (isset($decoded[$responseName][$elementName]['@attributes'])) {
$decoded[$responseName][$elementName]['@attributes']['xsi:type'] = "fgw:" . $elementName . 'Type';
}
}
//wrap data in a SOAP envelope
$decoded = [
'SOAP-ENV:Envelope' =>
['@namespaces' => [
"SOAP-ENV" => "http://schemas.xmlsoap.org/soap/envelope/",
"fgw" => "http://schemas.ferrygateway.org/1.3.1",
"xsi" => "http://www.w3.org/2001/XMLSchema-instance"
],
'SOAP-ENV:Body' => [$responseName => $decoded]
]
];
$encoded = element_encode($decoded);
$domDocument->loadXML($encoded);
}
)
);
});
}
}Which throws the following exception when sending a request: This exact middleware, however, was working perfectly in v2. <?xml version="1.0" encoding="utf-8"?>
<GetRoutesRequest OperatorCode="STENA" xmlns="http://schemas.ferrygateway.org/1.3.1">
<Context AgentAccountNumber="TEST" TimeStamp="2022-08-08T21:00:00" CountryCode="GBR" Currency="DKK" LanguagePrefCode="en" TransactionId="123456789ABC" ExternalBookingReference="EB12345" User="WEBSITE" />
</GetRoutesRequest>Ideally, there would be an option to send non-SOAP-wrapped requests with v4. If not, do you have any suggestions? |
|
That is basically what I was trying to say a few replies back : You are not really doing SOAP anymore. Given the fact that you are doing XML over HTTP, maybe I can suggest an alternative approach.
That way you can craft your own XML based on objects that is fully compatible with your webservice. This approach would remove all the overhead of trying to make the webservice act as-if it were a SOAP service. |
|
Thank you, @veewee, for your time and suggestions. We will definitely consider this approach in the future. |
Uh oh!
There was an error while loading. Please reload this page.
Uh oh!
There was an error while loading. Please reload this page.
I'm getting an error
Unable to find a usable service inside your WSDL.while trying to generate a classmap, even though my wsdl contains a service:Did anyone else came across this issue before? Any help would be appreciated.
All reactions