 | | | Fomatting question serializing DOM with pretty-print | Fomatting question serializing DOM with pretty-print 2007-06-29 - By Eric Kolotyluk
Here is an example of our traffic log using XMLSerializer
2007-06-26 13:22:16.066
<?xml version="1.0" encoding="UTF-8"?>
<User clientName="EKolotyluk_380" clientPlatform="Windows XP (5.1)"
clientProtocolVersion="{DB4AEBDF-A4A9-4521-880B-02310D12723B}"
clientType="Admin" clientVersion="0.0.0.0"
cookie="1a741296:11369b28de8:-7fd8" isoLanguageCode="en"
sendCompressed="true" type="checkProtocolVersion"/>
2007-06-26 13:22:16.379
<?xml version="1.0" encoding="UTF-8"?>
<Server cookie="1a741296:11369b28de8:-7fd8" deviceType="Admin"
failureText="Protocol Version not supported" friendlyName="CSMP2610"
ipAddress="10.1.41.70" licenseStatus="0"
macAddress="00-14-22-38-AA-43" result="Failed" serialNumber="09665"
type="checkProtocolVersion">
<VersionInfo>
<AdminServer versionBuild="23" versionMajor="3" versionMinor="1"
versionOther="5" versionPatch="5"/>
</VersionInfo>
<Event eid="85008" hr="0" timeStamp="1182889209"/>
</Server>
The time-stamp we add to the log. Here is the same XML using LSSerializer
2007-06-29 07:42:06.774
<?xml version="1.0" encoding="UTF-8"?><User clientName="EKolotyluk_380"
clientPlatform="Windows XP (5.1)"
clientProtocolVersion="{DB4AEBDF-A4A9-4521-880B-02310D12723B}"
clientType="Admin" clientVersion="0.0.0.0"
cookie="-7dfe3a9b:11377ee20de:-7fdd" isoLanguageCode="en"
sendCompressed="true" type="checkProtocolVersion"/>
2007-06-29 07:42:07.039
<?xml version="1.0" encoding="UTF-8"?><Server
cookie="-7dfe3a9b:11377ee20de:-7fdd" deviceType="Admin"
failureText="Protocol Version not supported" friendlyName="CSMP2610"
ipAddress="10.1.41.70" licenseStatus="0" macAddress="00-14-22-38-AA-43"
result="Failed" serialNumber="09665" type="checkProtocolVersion">
<VersionInfo>
<AdminServer versionBuild="23" versionMajor="3" versionMinor="1"
versionOther="5" versionPatch="5"/>
</VersionInfo>
<Event eid="85008" hr="0" timeStamp="1183127997"/>
</Server>
The first obvious problem is that the first element of our document does not
have a linebreak before it - it's on the same line as the <?XML ... ?>
The second obvious problem is that element with a long list of attributes
are not wrapped and indented. They should be wrapped after some reasonable
line limit (i.e. 60, 80, 100 characters - pick one). It would be nice if
there was a way to specify this through the API. Also, when they are
wrapped, they should be intented.
What I tried to imply is that whatever XMLSerializer is doing now, make
LSSerializer do the same thing at least.
Cheers, Eric
keshlam wrote:
>
>>the pretty-printing is so bad - it's not all that pretty.
>
> If you were specific about what you want done differently, that would be
> helpful.
>
> Note too that if you want *really* pretty, the right answer may be to
> write
> a stylesheet that expresses precisely the formatting you want rather than
> taking the (relatively simple-minded) default.
>
> ______________________________________
> "... Three things see no end: A loop with exit code done wrong,
> A semaphore untested, And the change that comes along. ..."
> -- "Threes" Rev 1.1 - Duane Elms / Leslie Fish
> (http://www.ovff.org/pegasus/songs/threes-rev-11.html)
>
--
View this message in context: http://www.nabble.com/Fomatting-question
-serializing-DOM-with-pretty-print-tf3252607.html#a11361625
Sent from the Xalan - J - Users mailing list archive at Nabble.com.
|
|
|