SAXException while parsing a well formed XML

[Priya Lavti]

Hi all,

I am getting SAXException while parsing even though my XML is well formed. I am using DOM parser here.
It is written in the API that SAXException can be thrown for both error and warning. Is there any way to ignore the warnings coming while parsing and hence no SAXException is thrown.

One more weird behavior I am getting is that when I catch the SAXException, it executes the catch block and after that control goes to the next line from where the exception was thrown, and that line is in try block itself. I'll show this with code example:

1.Try {
2.   DocumentBuilder docBuild = DocumentBuilderFactory.newInstance().newDocumentBuilder();
3.   Document document = docBuild.parse( inputSrc );      //SAXException is thrown on this line
4.   //Some code�
5.�
6.} catch (Exception e) {
7.   System.out.println(�Exception while parsing: �+e.getMessage);
8.}
9.//Some Code�

Ideally when SAXException is thrown on line 3, control should go to the line 7 and the to line 9 after the catch block. But in current senario control is going to line 4 after line 7. It is something very strange happening. My guess is, is it because of some property of SAXException, when thrown for warning?

Any suggetion/advice in this regard will be helpful.
Thanks in advance

[Paul Sturrock]

My guess is, is it because of some property of SAXException, when thrown for warning?

If the code in your catch block is not being run then its not a SAXException that is being thrown. Could you post the stack trace you see?

[Priya Lavti]

SAXException is thrown and control is also going to catch block.
But after that its returning back to try block... that is what strange here...

[Paul Sturrock]

That sort of behaviour is against the core control mechanisms of Java. Are you sure this is what is happening, and if so how are you sure?

Also, could you post the stack trace you see? Its is much easier to talk about an Exception when we can see the message you see.

[Priya Lavti]

yes I am sure, coz I was actually having System.out.println (SOP) in both the place, catch block and try block. And 1st it is pritning the SOP of catch followed by of the try block.

[B]11:55:54,557 INFO  [STDOUT] *********Exception in TransmitConfirm.jsp:::: Exception[/B]11:55:54,557 INFO  [STDOUT]  : Failed to initialize transmit module : Content is not allowed in prolog.
11:55:54,557 INFO  [STDOUT] at com.device.systemmanagement.transmit.TransmitManager.<init>(TransmitManager.java:101)
11:55:54,557 INFO  [STDOUT] at com.device.systemmanagement.transmit.TelephoneTransmitManager.<init>(TelephoneTransmitManager.java:84)
11:55:54,557 INFO  [STDOUT] at org.apache.jsp.telephone.TransmitConfirm_jsp._jspService(org.apache.jsp.telephone.TransmitConfirm_jsp:362)
11:55:54,557 INFO  [STDOUT] at org.apache.jasper.runtime.HttpJspBase.service(HttpJspBase.java:97)
11:55:54,557 INFO  [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
11:55:54,557 INFO  [STDOUT] at org.apache.jasper.servlet.JspServletWrapper.service(JspServletWrapper.java:322)
11:55:54,557 INFO  [STDOUT] at org.apache.jasper.servlet.JspServlet.serviceJspFile(JspServlet.java:314)
11:55:54,557 INFO  [STDOUT] at org.apache.jasper.servlet.JspServlet.service(JspServlet.java:264)
11:55:54,557 INFO  [STDOUT] at javax.servlet.http.HttpServlet.service(HttpServlet.java:810)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:252)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
11:55:54,557 INFO  [STDOUT] at org.jboss.web.tomcat.filters.ReplyHeaderFilter.doFilter(ReplyHeaderFilter.java:81)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:202)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:173)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:213)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:178)
11:55:54,557 INFO  [STDOUT] at org.jboss.web.tomcat.security.CustomPrincipalValve.invoke(CustomPrincipalValve.java:39)
11:55:54,557 INFO  [STDOUT] at org.jboss.web.tomcat.security.SecurityAssociationValve.invoke(SecurityAssociationValve.java:153)
11:55:54,557 INFO  [STDOUT] at org.jboss.web.tomcat.security.JaccContextValve.invoke(JaccContextValve.java:59)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:126)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:105)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:107)
11:55:54,557 INFO  [STDOUT] at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:148)
11:55:54,557 INFO  [STDOUT] at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856)
11:55:54,557 INFO  [STDOUT] at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.processConnection(Http11Protocol.java:744)
11:55:54,557 INFO  [STDOUT] at org.apache.tomcat.util.net.PoolTcpEndpoint.processSocket(PoolTcpEndpoint.java:527)
11:55:54,557 INFO  [STDOUT] at org.apache.tomcat.util.net.MasterSlaveWorkerThread.run(MasterSlaveWorkerThread.java:112)
11:55:54,557 INFO  [STDOUT] at java.lang.Thread.run(Thread.java:595)
[B]11:55:54,791 INFO  [STDOUT] Task: Deleting the Device[/B]

Here I have caught the SAXException at TransmitManager in a catch block and then throwing my user defined exception and catching that into the jsp file.

And also the 1st line in bold is in the catch block and the last line is in the try block. That is why I am sure controling is flowing from catch block to try block.

[Paul Sturrock]

And also the 1st line in bold is in the catch block and the last line is in the try block. That is why I am sure controling is flowing from catch block to try block.

Are you sure? Again what you are suggesting would mean that the basic, well understood and extremely well tested control mechanisms in the Java language were broken. If it were me, I would be more inclined to think I had made a mistake, rather than Java is behaving in a way it has never behaved before.

FYI - your exception is almost certainly because you have leading whitespace in your XML file, though I can't be 100% sure. I'm guessing that the code you posted is not the code you are running (I don't see the message "Exception while parsing:" anywhere in the stack trace). Could you post the real code?