After a bit of testing, the fix I proposed above fixes :
=> no more _BADXML files due to character set error when parsing XML data files
but now it generates some garbage characters because the server doesn't seem to know that these are iso-8859-1 encoded data text, so in the pandora console I can not see the accentuated characters, but only things like "DÃ�©marrage" instead of "Démarrage".
So problem remains entirely.
It may be added in the bug reports.
bye for now
Hi dennis, try to use "<![CDATA[]]>" ( as example, <data><![CDATA[my_data ]]</data> also read
http://www.w3schools.com/xml/xml_cdata.asp)
EDIT: Well, this should be changed into the pandora agent config file. :-D
I haven't tested it, but the xml parser "should" not have errors :-D)
About the .data, yes we were thinking about adding the <?xml headers, but until this moment we haven't got any time to modify them.
Also we have written some xsl and dtd to view the info there:
Add to the data file:
[code:1]<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE agent_data SYSTEM "pandora_agent.dtd">
<?xml-stylesheet href="pandora_agent.xsl" type="text/xsl"?>[/code]
file pandora_agent.dtd:
[code:1]<!ELEMENT agent_data (module*)>
<!ATTLIST agent_data
os_name CDATA #REQUIRED
os_version CDATA #REQUIRED
intervalo CDATA #REQUIRED
version CDATA #REQUIRED
timestamp CDATA #REQUIRED
agent_name CDATA #REQUIRED>
<!ELEMENT module (name, type, data)>[/code]
file pandora_agent.xsl:
[code:1]<?xml version="1.0" encoding="UTF-8"?>
<xsl:stylesheet version="1.0" xmlns:xsl="http://www.w3.org/1999/XSL/Transform">
<xsl:template match="/">
<html>
<head><title>Pandora Agent</title></head>
<body>
<table border="1">
<tr>
<th>Name</th>
<th>Type</th>
<th>Data</th>
</tr>
<xsl:for-each select="agent_data/module">
<tr>
<td><xsl:value-of select="name"/></td>
<td><xsl:value-of select="type"/></td>
<td><xsl:value-of select="data"/></td>
</tr>
</xsl:for-each>
</table>
</body>
</html>
</xsl:template>
</xsl:stylesheet>[/code]
If you do that, you can see data in browser, just for fun :-D
Raul
