This message is in MIME format. Since your mail reader does not understand
this format, some or all of this message may not be legible.
Looks like I mistitled this thread. The proposal is _not_ to remove the summary information from the XML output. The proposal is to replace the HTML representation of the summary information in the XML output with an XML representation.
Data in the HTML summary report is not easily accessible. The report is within a CDATA block, which means that it's just one long string to an XML parser. The report can be extracted into a separate file, but it's not valid XML, so it still can't be parsed as-is. Even if it were to be fixed up so that it could be parsed (which wouldn't be too hard), the structure of the data isn't meaningful. For example, the XPath _expression_ to extract the list of package names is '//h2/i/font/text()'. The XPath to extract the summary data for a package would be much more complicated, since there's no element holding all the data for a package.
During program execution, FindBugs first generates summary report data as XML, then transforms the XML into HTML using the stylesheet in etc/summary.xsl. So this patch would insert the original summary XML, instead of the transformed summary HTML, into the XML file. The summary.xsl stylesheet (or one of the other report stylesheets) could still be used to produce the HTML summary report in a step after FindBugs completion.
jay
-----Original Message-----
From: findbugs-discuss-bounces@xxxxxxxxxx [mailto:findbugs-discuss-bounces@xxxxxxxxxx] On Behalf Of Glenn Boysko
Sent: Wednesday, February 09, 2005 12:45 PM
To: Find Bugs Discussion
Subject: [FB-Discuss] Re: Removing HTML from XML output
Hello All:
Regarding the presence of HTML in the result file, I would argue against it.
We use Find Bugs from within Cruise Control and store the result XML file as an
artifact of the build process. To aid in viewing the results, we simply
extract the summary HTML for display purposes. For developers, they download
the XML file and use it for further viewing via the Find Bugs Swing GUI.
What is the real problem with having it embedded in the XML file? It doesn't
prevent any programmatic access to the XML results. It can still be parsed by
any XML parser, right?
Regards,
Glenn
__________________________________
Do you Yahoo!?
All your favorites on one personal page - Try My Yahoo!
http://my.yahoo.com
_______________________________________________
Findbugs-discuss mailing list
Findbugs-discuss@xxxxxxxxxxxxxxxx
http://mailman.cs.umd.edu/mailman/listinfo/findbugs-discuss
| 
