On 13/11/2013 22:08, huizhe wang wrote:
:
Each parser has its own copy of XMLSecurityManager that maintains the
values of the limits. The parser is reset before it starts to parse a
document. Resetting the values managed by XMLSecurityManager therefore
makes sure that the limits are per
Hi Joe,
The new webrev looks good...
-- daniel
On 11/13/13 11:08 PM, huizhe wang wrote:
On 11/13/2013 1:33 PM, Alan Bateman wrote:
On 13/11/2013 20:02, huizhe wang wrote:
Hi,
The issue is that the limits applied to each processing process
rather than each file processing. This applies to
Hi,
The issue is that the limits applied to each processing process rather
than each file processing. This applies to not only StAX as reported,
but also other parsers and validators. The fix is to add reset to
XMLSecurityManager and call it upon each file processing. XSLT Transform
is
On 13/11/2013 20:02, huizhe wang wrote:
Hi,
The issue is that the limits applied to each processing process rather
than each file processing. This applies to not only StAX as reported,
but also other parsers and validators. The fix is to add reset to
XMLSecurityManager and call it upon each
looks fine joe
On Nov 13, 2013, at 3:02 PM, huizhe wang wrote:
Hi,
The issue is that the limits applied to each processing process rather than
each file processing. This applies to not only StAX as reported, but also
other parsers and validators. The fix is to add reset to
On 11/13/2013 1:33 PM, Alan Bateman wrote:
On 13/11/2013 20:02, huizhe wang wrote:
Hi,
The issue is that the limits applied to each processing process
rather than each file processing. This applies to not only StAX as
reported, but also other parsers and validators. The fix is to add
reset
