[jdom-interest] SAXBulder Problem
mark.hortman at jcafeinc.com
Wed Jul 24 11:32:52 PDT 2002
I just found out why it is doing this and thought I would pass it along to
the rest of the world....
It seems that some of my users had Microsoft's WSP (WinSock Proxy Client)
installed, and my applet worked fine, but when the same users had IE going
through the same proxy server(via IE Settings), my applet was being told by
the proxy server that it wasn't authenticated. This message was an html
page with <META> in it. Once I turned off the IE use proxy and let WSP
handle the proxy all was right with the world.
From: Alex Rosen [mailto:arosen at silverstream.com]
Sent: Wednesday, July 24, 2002 12:23 PM
To: Mark Hortman; jdom-interest at jdom.org
Subject: RE: [jdom-interest] SAXBulder Problem
Sounds like you're passing an HTML stream into SAXBuilder, not an XML
stream. It's seeing an HTML <META> tag and choking (since this tag doesn't
have an end tag </META> in HTML). You'll have to figure out why the input
stream doesn't contain what you're expecting it to contain.
From: jdom-interest-admin at jdom.org [mailto:jdom-interest-admin at jdom.org]On
Behalf Of Mark Hortman
Sent: Wednesday, July 24, 2002 9:56 AM
To: 'jdom-interest at jdom.org'
Subject: [jdom-interest] SAXBulder Problem
I am getting the following error.
org.jdom.JDOMException: Error on line 4: The element type "META" must be
terminated by the matching end-tag "</META>".
I DON'T HAVE A META TAG IN MY XML FILE AT ALL.
I am running in an applet, and have xerces.jar in my list of jars.
I am calling SAXBulder.build with an bufferedReader, which is coming into an
applet from a server.
I am using jdom-dev.jar from another project, and appears to be from a June
20, 2002 nightly build of JDom the best I can tell.
Question 1, When I look at SAXBulder.java, I don't see line 650 as an
executable line of code.
When I go back many versions of SAXBuilder I still don't see line 650
inside of build, what is the deal?
Question 2, What could be causing this? My applet appears to work on some
machines and some servers, like my development machine,
but not others.
More information about the jdom-interest