View Single Post
  #1 (permalink)  
Old July 6th, 2002
javier__d javier__d is offline
Devotee
 
Join Date: June 29th, 2001
Location: Slovakia
Posts: 24
javier__d is flying high
Exclamation Problem (bug?) in 0.7.2

Hi.

I started 0.7.2 and it was great. But after exiting it doesn't start anymore, with error message:

Global(Severe)! Exception occured: org.xml.sax.SAXParseException: Illegal XML character: .
at org.apache.crimson.parser.InputEntity.fatal(InputE ntity.java:1038)
at org.apache.crimson.parser.InputEntity.parsedConten t(InputEntity.java:593)
at org.apache.crimson.parser.Parser2.content(Parser2. java:1747)
at org.apache.crimson.parser.Parser2.maybeElement(Par ser2.java:1468)
at org.apache.crimson.parser.Parser2.content(Parser2. java:1700)
at org.apache.crimson.parser.Parser2.maybeElement(Par ser2.java:1468)
at org.apache.crimson.parser.Parser2.content(Parser2. java:1700)
at org.apache.crimson.parser.Parser2.maybeElement(Par ser2.java:1468)
at org.apache.crimson.parser.Parser2.content(Parser2. java:1700)
at org.apache.crimson.parser.Parser2.maybeElement(Par ser2.java:1468)
at org.apache.crimson.parser.Parser2.content(Parser2. java:1700)
at org.apache.crimson.parser.Parser2.maybeElement(Par ser2.java:1468)
at org.apache.crimson.parser.Parser2.parseInternal(Pa rser2.java:499)
at org.apache.crimson.parser.Parser2.parse(Parser2.ja va:304)
at org.apache.crimson.parser.XMLReaderImpl.parse(XMLR eaderImpl.java:433)
at org.apache.crimson.jaxp.DocumentBuilderImpl.parse( DocumentBuilderImpl.java:179)
at javax.xml.parsers.DocumentBuilder.parse(DocumentBu ilder.java:86)
at phex.xml.XMLBuilder.loadFromStream(Unknown Source)
at phex.xml.XMLBuilder.loadFromFile(Unknown Source)
at phex.download.swarming.SwarmingManager.loadDownloa dList(Unknown Source)
at phex.MainFrame.<init>(Unknown Source)
at phex.gui.common.GUIRegistry.initialize(Unknown Source)
at phex.f.main(Unknown Source)

I think it's a problem of a vendor name of some client/server that is sometimes in my download candidates. In my download.xml file it's given as <vendor>ÃÂ*.P.</vendor>
where the name itself is (in hexadecimals)
c3 a0 18 50 00

Perhaps it's chinese or something similar. Anyway phex can't get through it.
For the moment, removing all vendor lines containing these problematic name from my phexdownload.xml by hand fixed the problem and phex started again. I don't know if it's ok not to have vendor line, but I imagine it should be only an additional information not really needed. Am I right?

I think phex should check vendor name before storing it.
What do You think?

Javier
Reply With Quote