Symptom
You notice a change in the structure of the SFAPI payload starting CW43 or CW44 2022 (e.g. there seems to be a duplicate namespace)
This may be causing issues, e.g. parsing errors in the client application.
Sample Code:
Before
---------
<?xml version='1.0' encoding='UTF-8'?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/">
<S:Body>
<loginResponse xmlns="urn:sfobject.sfapi.successfactors.com" xmlns:ns2="urn:fault.sfapi.successfactors.com">
<result>
<sessionId>redacted</sessionId>
<msUntilPwdExpiration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
</result>
</loginResponse>
</S:Body>
</S:Envelope>
After
-------
<?xml version="1.0" ?>
<S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/">
<SOAP-ENV:Header/>
<S:Body>
<loginResponse xmlns="urn:sfobject.sfapi.successfactors.com" xmlns:ns2="urn:fault.sfapi.successfactors.com">
<result>
<sessionId>redacted</sessionId>
<msUntilPwdExpiration xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" xsi:nil="true"/>
</result>
</loginResponse>
</S:Body>
</S:Envelope>
Environment
SAP SuccessFactors SFAPI
Cause
Expected behaviour
Resolution
You may observe this behaviour after SAP SuccessFactors performed a JKD11 upgrade in our servers during CW 43-44 2022, however this is the expected behaviour from JDK (meaning, everyone should follow this format/spec as per XML spec at: https://www.w3schools.com/xml/xml_syntax.asp )
Please adopt these XML file changes to comply with the XML spec.
Keywords
<?xml version="1.0" encoding="utf-8"?>, XML, encoding attribute, removed, missing, standard XML declaration, XML declaration, namespace, attribute encoding, JKD11, JKD11 upgrade, JDK, https://www.w3schools.com/xml/xml_syntax.asp ),XML, XML spec, <S:Envelope xmlns:S="http://schemas.xmlsoap.org/soap/envelope/" xmlns:SOAP-ENV="http://schemas.xmlsoap.org/soap/envelope/"> , KBA , LOD-SF-INT-API , API & Adhoc API Framework , LOD-SF-INT , Integrations , Problem