Jump to content
Claris Engage 2025 - March 25-26 Austin Texas ×

XSLT/XML Transformation - Encoding Issues


This topic is 6312 days old. Please don't post here. Open a new topic instead.

Recommended Posts

  • Newbies
Posted

We just updated to 9.0 and have encountered several new issues with custom web publishing when it comes to encoding of XML. We serve via http: XML data which in 8.0 was encoded to ISO-8859-1. Now in 9.0 is defaults to UTF-8 and to change this we have to create a XSLT style sheet with the encoding method specified. We are good on that.

But now, the XML being published when validated on our SQL server gives us an interesting new port error. FMP appended a port :0

Has anyone encountered this and how do you change this? Seems very inside and obviously there are not any settings for this. It is coming from the web publishing setting.

//FMI//DTD fmresultset//EN " http://pandaecom.pandacommunications.com:0/fmi/xml/fmresultset.dtd >

It should read as //FMI//DTD fmresultset//EN " http://pandaecom.pandacommunications.com/fmi/xml/fmresultset.dtd >

And of course you can't change this as it is the web engine that is publishing this.

Oh yeh, the flavor of XML changed to which if anyone is publishing XML you need to update your transformation on the other end to accept the new xml from FMP. Our SQL server totally choked on all of this and the docs in FMP are not real clear of the problems in upgrading.

This topic is 6312 days old. Please don't post here. Open a new topic instead.

Create an account or sign in to comment

You need to be a member in order to leave a comment

Create an account

Sign up for a new account in our community. It's easy!

Register a new account

Sign in

Already have an account? Sign in here.

Sign In Now
×
×
  • Create New...

Important Information

By using this site, you agree to our Terms of Use.