using SAX1, SAXParser, or SAXParserFactory. Use XMLReader and
XMLReaderFactory instead.
--
Elliotte Rusty Harold
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
but they have also listed the
> JAXP impl bundled in the JDK (which I know is no longer Xerces).
>
Really? Since when. I know it used to be Xerces, and I thought it
still was (modulo Sun patches and repackaging). In what version did
this change?
--
Elli
ve any effect on this. That feature protects against parsers
following the spec, and expanding entity references. It sounds like
the problem here is a failure to follow the spec, and blowing up on
malformed, recursive entity declarations; though, as I said, I'm only
g
t sure what you're using, but nothing in this sample is SAX. It
sounds like there's some higher level API sitting on top of SAX doing
something ill-advised. Were you to rewrite this app to use real SAX,
you could first use a single pass to grab all the values you need; and
then fill the cel
orked.
> But I think, the problem I mentioned is likely an Eclipse IDE problem (I'm
> using the 2014 edition). I had given the XSD 1.1 project as a dependency to
> my own project, and this should have provided xml-apis.jar t
t; not found. Can someone please suggest, how I can fix this? I've also tried
> starting Eclipse with option -clean, but that doesn't help. Its been 1-2
> weeks, that I'm trying to solve this problem, but haven't found solution yet
> :( I would be happy for any help.
>
Hello Team,
>
> Is it possible to implement validations on the basis of XML size or time
> taken to parse the XML file?
>
> Regards,
--
Elliotte Rusty Harold
elh...@ibiblio.org
-
To unsubscribe
