You can use any XSLT engine to do this type of transformation, but I chose to use Microsoft's command-line utility, msxsl, to do this.ġ) Before I did anything else, I had to re-generate the XML from SQL Developer so the DATA type data values would be in the canonical date format used by Application Express XML data loading. I'm no XSLT expert, but I learned enough from Carl's examples to accomplish this type of simple transformation. So how do we transform the XML from SQL Developer into something compatible with the standard ROWSET format used by Application Express? Well.this is exactly what XSLT was designed for. Maybe there's a way to control this in SQL Developer, but I'm not aware of it. SQL Developer, for whatever reason, uses a different format.
Underneath the hood, Application Express uses DBMS_XMLSAVE.INSERTXML for the XML loading, and it uses the default ROWSET and ROW tags. It isn't that Application Express didn't like the CDATA elements, it's just that they are two completely different XML formats. He originally thought that Application Express was choking on the CDATA values. Using the EMP table as an example, he showed me that the data he exported from SQL Developer looked something like:
He pointed me to his post on the Oracle Application Express discussion forum on OTN. Gary, an Application Express customer for many years, recently sent me a message with a problem he was having getting table data, exported from Oracle SQL Developer in XML format, into Oracle Application Express.
0 kommentar(er)
