I am trying to migrate few Lucee 4 applications to Lucee 184.108.40.206 where we are facing this problem every time an XML object is converted to string either using toString() method or an implicit conversion by CFFunction with access=“remote” and returnType=“string” .
With Lucee 4 The XML declaration is like this
<?xml version="1.0" encoding="UTF-8"?>
and with Lucee 5.3.x we get the new XML declaration which is
<?xml version="1.0" encoding="UTF-8" standalone="no"?>
While technically there should be no harm in retaining the new “standalone” attribute in the resulting XML of our SOAP responses, we want the result to be as close as it was with LUCEE 4 for the consumers who rely on exact response packets.
Is there any way to tell LUCEE to not introduce this new attribute in XML. For example in Application setting such as this.serialization
OS: Windows 2019
Java Version: 11.0.7 (AdoptOpenJDK) 64bit
Tomcat Version: Apache Tomcat/9.0.35
Lucee Version: 220.127.116.11