Skip to content

Conversation

veewee
Copy link
Member

@veewee veewee commented Aug 29, 2025

Q A
Type bug
BC Break no
Fixed issues phpro/soap-client#585

Summary

Fixes phpro/soap-client#585

<xs:schema xmlns="http://www.capita-software-services.com/scp/simple"
           xmlns:scpbase="http://www.capita-software-services.com/scp/base"
           xmlns:xs="http://www.w3.org/2001/XMLSchema" attributeFormDefault="unqualified"
           elementFormDefault="qualified" targetNamespace="http://www.capita-software-services.com/scp/simple">
    <xs:import namespace="http://www.capita-software-services.com/scp/base"/>
    <xs:element name="scpSimpleQueryRequest" type="scpbase:scpQueryRequest"/>
<xs:schema>

Previously, this resulted in the element scpSimpleQueryRequest being targeted to the scpbase namespace.
This is not correct, given that the element is axtyally in the simple namespace, which results in the type collection not being able to find this element. (only the complexType in scpbase).

This fixes that issue and makes sure the element is also encoded as scpSimple in the encoder.

@veewee veewee force-pushed the always-use-element-namespace-as-target branch from 6dfbb03 to a201d82 Compare August 29, 2025 05:58
@veewee veewee force-pushed the always-use-element-namespace-as-target branch from ac18f9d to 4e456c6 Compare August 30, 2025 12:30
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

Client is expecting MixedResult for some reason.
1 participant