Aleksander Slominski wrote:
> wouldnt it be better to throw an exceptionif user tries to set
> features that are not allowed in this state of the parser?
You're absolutely right -- someone just needs to implement it.
I'm waiting for your patches. :)
> it just took me a bit of time to figure out
Andy Clark wrote:
> The notifications are made BUT there are certain features
> and properties that are not allowed to be set during parsing.
> Some of these include the "namespaces" and "validation"
> features. In the case of the pull-parser configuration, when
> you call setInputSource, that is
Aleksander Slominski wrote:
> interesting information however it seems that time between setInputSource
> and parse(false) in XMLPullParserConfiguration is a "black hole" -
> parse(false) does not take into account anything that happened after
> setInputSource.
The notifications are made BUT ther
Andy Clark wrote:
> The call to setFeature will not be ignored. The XNI Manual
> in the documentation states:
>
> Before parsing a document, a parser configuration must use
> the component manager to reset all of the parser components.
> Then, during parsing, each time a feature or property
Aleksander Slominski wrote:
> setInputSource(...)
> setFeature(...)
> parse(true/false)
>
> and the call to setFeature will be ignored as features are evaluated
The call to setFeature will not be ignored. The XNI Manual
in the documentation states:
Before parsing a document, a parser configur
hi,
i think it is not really documented in API but XMLParserConfiguration
setFeature method is not really evaluated until setInputSource is called.
so in XMLPullParserConfiguration it is possible to have this
setInputSource(...)
setFeature(...)
parse(true/false)
and the call to setFeature will
