Re: SAX: finalising org.sax.xml.Parser

Juergen Modre (jmodre@edu.uni-klu.ac.at)
Tue, 24 Feb 1998 23:37:15 +0000

David Megginson wrote:
>
> Juergen Modre writes:
>
> > > In an ideal world, we'd also have some kind of ability to ask to
> > > parser to turn validation on or off, but I'm not certain that that's
> > > practical: any thoughts?
> > I thinks that is practical and necessary.
> >
> > One solution would be to have methods like:
> > void setValidation(boolean validation)
> > boolean getValidation()
> >
> > These methods can be called before starting to parse with
> > the parse() method.
>
> It's trickier than this -- for example, we'd probably have to create
> an exception that is thrown if the underlying parser does not support
> validation;
Correct. My example was just a first naive try.

> furthermore, none of the parsers that I've looked at
> supports a toggle like this, and we will be forcing another design
> decision on them if we require this toggle.
There are already XML parsers allowing this toggle.
For instance DXP has this capability.

I think it would be good to have methods that allow to
set a parser into well-formedness or validation mode.

> > I also think a parse method with an systemId only as parameter would be
> > convenient. (With targeting to users rather new to XML
> > and not very used to the publicId's).
> >
> > public abstract void parse (String systemId)
> >
> > This would also avoid the need to call every time
> > entityHandler.resolveEntity() to resolve the Entity.
>
> It might be simpler, though I'm trying to keep the number of methods
> to a minimum.
Okay.

All the best
Juergen

-----------------------------------------------
JUERGEN MODRE
Reisdorf 6
A-9371 Brueckl
Austria (Europe)

Phone: ++43 4214 2320
Mobile: ++43 664 233 22 22
E-mail: jmodre@edu.uni-klu.ac.at
WWW: http://www.edu.uni-klu.ac.at/~jmodre
-----------------------------------------------