David Sinclair wrote:
To help you reproduce the problem I have made the simplest example I could think of that exhibits the problem. Attached is an xforms-model.xml file and a view.xpl for the same page. Put an entry in a page view controller that uses these 2 files. The important thing about the example is that the output from the xslt contains unmatched text nodes: it is not well formed xml. The problem is that orbeon studio displays the output incorrectly. When the output of the xslt is saved to disk using the file serialiser you get:
David,
I am still having troubles reproducing the issue. Why are you saying the XSLT produces XML that is not well formed? It matches on the "message" element and produces a <message/>. Unless there are multiple "message" elements in the input document, the XSLT output will be well formed. And if you use your instance as the input, you should be fine as there is only one <message/>.
Now if there were 2 or more <message> elements in the input, you would have an exception telling you: "Cannot add another element to this Document as it already has a root element of: message".
Alex
-------------------------------------------------------
SF email is sponsored by - The IT Product Guide
Read honest & candid reviews on hundreds of IT Products from real users.
Discover which products truly live up to the hype. Start reading now. http://productguide.itmanagersjournal.com/
_______________________________________________
orbeon-user mailing list
[EMAIL PROTECTED]
https://lists.sourceforge.net/lists/listinfo/orbeon-user
