Thanks. Good to know.
Bob
Michael Glavassevich wrote:
Hi Bob,
Applications are already able to set an upper bound on maxOccurs. All you
have to do is register a SecurityManager [1][2] on an instance of the
parser and call setMaxOccurNodeLimit(int) on the SecurityManager
with the desired limit.
[1]
Hi Bob,
Applications are already able to set an upper bound on maxOccurs. All you
have to do is register a SecurityManager [1][2] on an instance of the
parser and call setMaxOccurNodeLimit(int) on the SecurityManager
with the desired limit.
[1] http://xml.apache.org/xerces2-j/properties.html#secu
Just a comment. Xerces' handling of large maxOccurs values seems pretty
broken. When I debugged into it, I discovered that the outofmemory
exceptions were caused by Xerces trying to allocate, IIRC, a table with
dimensions 19*19.
Yes, you can always tell the user to use "unbounded", but
