Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 188012 - Parsing exception from help file
Summary: Parsing exception from help file
Status: RESOLVED DUPLICATE of bug 196216
Alias: None
Product: Web Tools
Classification: WebTools
Component: documentation (show other bugs)
Version: 2.0   Edit
Hardware: PC Windows XP
: P3 normal with 1 vote (vote)
Target Milestone: ---   Edit
Assignee: Kate Price CLA
QA Contact: Kate Price CLA
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2007-05-20 20:52 EDT by David Williams CLA
Modified: 2008-01-30 19:00 EST (History)
1 user (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description David Williams CLA 2007-05-20 20:52:39 EDT
I tried clicking on a link title "Configuring XDoclet annotation support" and got the exception pasted below. 

So, 1) Kate, we seem to have invalid markup? 
and 2) Kate, if you agree, please open a bug on base Help, that it would be better if such an error occurs to display a friendlier message (such as "sorry, help is not available for that topic") and simply write the ugly info to the log. 


An error occured while processing the requested document: 

org.xml.sax.SAXParseException: The element type "p" must be terminated by the matching end-tag "</p>".
	at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
	at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
	at org.eclipse.help.internal.dynamic.DocumentReader.read(DocumentReader.java:56)
	at org.eclipse.help.internal.dynamic.XMLProcessor.process(XMLProcessor.java:49)
	at org.eclipse.help.internal.xhtml.DynamicXHTMLProcessor.process(DynamicXHTMLProcessor.java:66)
	at org.eclipse.help.internal.webapp.servlet.DynamicXHTMLFilter$1.close(DynamicXHTMLFilter.java:79)
	at java.io.FilterOutputStream.close(FilterOutputStream.java:160)
	at org.eclipse.help.internal.webapp.servlet.FilterHTMLHeadAndBodyOutputStream.close(FilterHTMLHeadAndBodyOutputStream.java:290)
	at org.eclipse.help.internal.webapp.servlet.EclipseConnector.transfer(EclipseConnector.java:136)
	at org.eclipse.help.internal.webapp.servlet.ContentServlet.doGet(ContentServlet.java:42)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:596)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
	at org.eclipse.equinox.http.registry.internal.ServletManager$ServletWrapper.service(ServletManager.java:177)
	at org.eclipse.equinox.http.servlet.internal.ServletRegistration.handleRequest(ServletRegistration.java:91)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.processAlias(ProxyServlet.java:110)
	at org.eclipse.equinox.http.servlet.internal.ProxyServlet.service(ProxyServlet.java:68)
	at javax.servlet.http.HttpServlet.service(HttpServlet.java:689)
	at org.eclipse.equinox.http.jetty.internal.HttpServerManager$InternalHttpServiceServlet.service(HttpServerManager.java:277)
	at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:428)
	at org.mortbay.jetty.servlet.ServletHandler.dispatch(ServletHandler.java:677)
	at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:568)
	at org.mortbay.http.HttpContext.handle(HttpContext.java:1530)
	at org.mortbay.http.HttpContext.handle(HttpContext.java:1482)
	at org.mortbay.http.HttpServer.service(HttpServer.java:909)
	at org.mortbay.http.HttpConnection.service(HttpConnection.java:820)
	at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:986)
	at org.mortbay.http.HttpConnection.handle(HttpConnection.java:837)
	at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:245)
	at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:357)
	at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:534)
Comment 1 Kate Price CLA 2008-01-30 19:00:24 EST
Dup of the more comprehensive 196216. There seems to be a glitch in the way Eclipse is reading certain div tags (files look fine locally but spew SAX parser errors in Eclipse infocenters). I think I've worked it out but I'm waiting until I see it in a build to confirm.

*** This bug has been marked as a duplicate of bug 196216 ***