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] http://xml.apache.org/xerces2-j/properties.html#security-manager [2] http://xml.apache.org/xerces2-j/javadocs/xerces2/org/apache/xerces/util/SecurityManager.html
On Mon, 22 Mar 2004, Bob Foster wrote:
It would be far better to pick a smaller upper bound by default and require an option to be set to go over it. This would allow you to produce an error message like "maxOccurs too large; use 'unbounded' instead" that the user could understand.
Bob
--------------------------- Michael Glavassevich XML Parser Development IBM Toronto Lab E-mail: [EMAIL PROTECTED] E-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
