{"id":655,"date":"2012-02-20T14:00:22","date_gmt":"2012-02-20T19:00:22","guid":{"rendered":"https:\/\/blogs.mathworks.com\/desktop\/?p=655"},"modified":"2012-02-21T08:37:49","modified_gmt":"2012-02-21T13:37:49","slug":"even-more-xml-and-matlab-controlling-xml-output","status":"publish","type":"post","link":"https:\/\/blogs.mathworks.com\/community\/2012\/02\/20\/even-more-xml-and-matlab-controlling-xml-output\/","title":{"rendered":"Even More XML and MATLAB : Controlling XML Output"},"content":{"rendered":"

I’ve had a lot of comments in the past few months about MATLAB’s XML functionality, so I guess it’s time to provide a few more posts on the matter. Today is part 4 of the series, this time covering some of the limitations of xmlwrite<\/tt><\/a>.<\/p>\n

XMLWRITE is MATLAB’s function for serializing the document element. With just one argument, the xml content is printed to the Command Window. With two arguments that data is saved to a text file. This function doesn’t give you a lot of room to customize the output; we pretty much expect that most MATLAB users will want the default. However, there are times when you’ll need a little extra control over the output. The advanced concept here is that although you create an XML document object in the MATLAB workspace, the output is really controlled by a Java serializer object, and does not use all of the document’s properties. XMLWRITE creates and executes the serializer for you. To customize this process you’ll have to manage the serialization yourself using MATLAB’s Java interface.<\/p>\n

In particular, the properties set on the XML node in the output file are set by the serializer and not the DOM object passed to XMLWRITE. This limitation was encountered by some of my blog’s commenters and users of MATLAB Answers. For an example, see this MATLAB Answers post: “setXmlStandalone bug?<\/a>.” The workaround I presented in that post, I’ve duplicated below. Fair warning, this is an advanced Java maneuver. <\/p>\n

docNode = com.mathworks.xml.XMLUtils.createDocument('AddressBook'<\/span>);\r\ndocNode.getDocumentElement.appendChild(docNode.createElement('b'<\/span>));\r\ndocNode.getDocumentElement.appendChild(docNode.createElement('a'<\/span>));\r\n%don't do this docNode.setXmlStandalone(1)<\/span>\r\n\r\nimport javax.xml.transform.*<\/span>;\r\nimport javax.xml.transform.dom.*<\/span>;\r\nimport javax.xml.transform.stream.*<\/span>;  \r\n\r\ntfactory = TransformerFactory<\/a>.newInstance;\r\ntransformer <\/a>= tfactory.newTransformer;\r\nsrc = DOMSource<\/a>(docNode);\r\nstream = java.io.StringWriter<\/a>;\r\ndst = StreamResult<\/a>(stream);\r\n\r\n%set the value here instead<\/span>\r\ntransformer.setOutputProperty(OutputKeys.STANDALONE,'yes'<\/span>);\r\ntransformer.setOutputProperty(OutputKeys.VERSION,'1.1'<\/span>);\r\ntransformer.setOutputProperty(OutputKeys.ENCODING,'ASCII'<\/span>);\r\n\r\ntransformer.transform(src,dst);\r\n\r\nresult = char(stream.toString)<\/pre>\n
\r\nresult =\r\n\r\n<?xml version=\"1.1\" encoding=\"ASCII\" standalone=\"yes\"?><AddressBook><b\/><a\/><\/AddressBook>\r\n\r\n<\/pre>\n
As you can see, from this code, setting the OutputProperty using OutputKeys<\/a> allows us to control what shows up in the final XML document. Properties set on docNode<\/tt> are ignored. In this example I use a StringWriter to get a String form of the XML, but you can use a FileWriter<\/a> to save it to disk.<\/p>\n
I’ve received some comments that this solution is not the friendly MATLAB code we’re used to, so I’ve created enhancement requests to bring some of this functionality into XMLWRITE.<\/p>\n
Other posts in the series:<\/p>\n