[XML-DEV Mailing List Archive Home] [By Thread] [By Date] [Recent Entries] [Reply To This Message]

Re: SAX and stuff ...

• From: Stefan Haustein <haustein@l...>
• To: "Xml-Dev (E-mail)" <xml-dev@l...>
• Date: Tue, 25 Jul 2000 20:19:49 +0200

Tony Pelton wrote:
> 
> 1. Is this a practical, reasonable and expected approach to doing SAX
> parsing for a handful of fairly simple but potentially large XML messages
> that we have brewed "in-house" and have not developed DTD's for ?
> (...)
> I then find myself thinking about the number of "if's" my code is performing
> on every startElement() ... and then I find myself putting the "if's" that I
> expect to get more of ... before the one's I expect less of ...

There are several options:

If you are building a tree of objects during parsing, 
you can perhaps map the element names to the classes 
using a hashtable and reflection (see Class.newInstance () etc..).

If you just want to save some time, you could use a switch statement
for the first character and skip some ifs this way (divide and conquer).

Another possibility could be to use a pull parser 
instead of sax. A pull parser works similar to a 
reader, so you can simply have different parsing 
methods for different contexts.

Best,

Stefan

-- 
Stefan Haustein             
Univ. Dortmund, FB 4, LS 8   tel: +49 231 755 2499
Baroper Str. 301             fax: +49 231 755 5105
D-44221 Dortmund (Germany)   www-ai.cs.uni-dortmund.deTony Pelton wrote:

• References:
  • SAX and stuff ...
    • From: Tony Pelton <tony.pelton@s...>

• Prev by Date: RE: Can an element be sometimes empty?
• Next by Date: RE: SOAP serialization
• Previous by thread: SAX and stuff ...
• Next by thread: Re: SAX and stuff ...
• Index(es):
  • Date
  • Thread