[jira] [Updated] (XERCESJ-1759) Add support for jdk.xml.maxElementDepth to SecureProcessingConfiguration.

[ https://issues.apache.org/jira/browse/XERCESJ-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1759: -- Summary: Add support for jdk.xml.maxElementDepth to SecureProcessingConfigura

[jira] [Updated] (XERCESJ-1759) Parsing xml cannot limit the maximum element depth, resulting in excessive memory usage and DOS.

[ https://issues.apache.org/jira/browse/XERCESJ-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1759: -- Issue Type: New Feature (was: Bug) > Parsing xml cannot limit the maximum el

[jira] [Comment Edited] (XERCESJ-1759) Parsing xml cannot limit the maximum element depth, resulting in excessive memory usage and DOS.

[ https://issues.apache.org/jira/browse/XERCESJ-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762173#comment-17762173 ] Michael Glavassevich edited comment on XERCESJ-1759 at 9/5/23 5:46 PM: --

[jira] [Comment Edited] (XERCESJ-1759) Parsing xml cannot limit the maximum element depth, resulting in excessive memory usage and DOS.

[ https://issues.apache.org/jira/browse/XERCESJ-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762173#comment-17762173 ] Michael Glavassevich edited comment on XERCESJ-1759 at 9/5/23 5:38 PM: --

[jira] [Commented] (XERCESJ-1759) Parsing xml cannot limit the maximum element depth, resulting in excessive memory usage and DOS.

[ https://issues.apache.org/jira/browse/XERCESJ-1759?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17762173#comment-17762173 ] Michael Glavassevich commented on XERCESJ-1759: --- I also view this as a fe

[jira] [Resolved] (XERCESJ-1755) Unicode character Fullwidth Plus Sign not allowed in attribute value (XML 1.0)

[ https://issues.apache.org/jira/browse/XERCESJ-1755?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1755. --- Resolution: Not A Bug The documentation for Xerces explicitly states that i

[jira] [Comment Edited] (XERCESJ-1751) Changing maxOccurs=unbounded to some finite number throws OOM in JVM

[ https://issues.apache.org/jira/browse/XERCESJ-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605519#comment-17605519 ] Michael Glavassevich edited comment on XERCESJ-1751 at 9/15/22 8:26 PM: -

[jira] [Commented] (XERCESJ-1751) Changing maxOccurs=unbounded to some finite number throws OOM in JVM

[ https://issues.apache.org/jira/browse/XERCESJ-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17605519#comment-17605519 ] Michael Glavassevich commented on XERCESJ-1751: --- There were some improvem

[jira] [Resolved] (XERCESJ-1751) Changing maxOccurs=unbounded to some finite number throws OOM in JVM

[ https://issues.apache.org/jira/browse/XERCESJ-1751?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1751. --- Resolution: Duplicate > Changing maxOccurs=unbounded to some finite number

[jira] [Comment Edited] (XERCESJ-1748) sonatype-2017-0348 - xerces:xercesImpl - Denial of Service (DoS)

[ https://issues.apache.org/jira/browse/XERCESJ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604876#comment-17604876 ] Michael Glavassevich edited comment on XERCESJ-1748 at 9/14/22 5:50 PM: -

[jira] [Commented] (XERCESJ-1748) sonatype-2017-0348 - xerces:xercesImpl - Denial of Service (DoS)

[ https://issues.apache.org/jira/browse/XERCESJ-1748?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17604876#comment-17604876 ] Michael Glavassevich commented on XERCESJ-1748: --- Xerces relies on the JDK

[jira] [Commented] (XERCESJ-1740) Make implementations of DOM collections (e.g.: `org.w3c.dom.NodeList`, etc.) implement `java.lang.Iterable`

[ https://issues.apache.org/jira/browse/XERCESJ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17497008#comment-17497008 ] Michael Glavassevich commented on XERCESJ-1740: --- It's been awhile, but I'

[jira] [Commented] (XERCESJ-1740) Make implementations of DOM collections (e.g.: `org.w3c.dom.NodeList`, etc.) implement `java.lang.Iterable`

[ https://issues.apache.org/jira/browse/XERCESJ-1740?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17496844#comment-17496844 ] Michael Glavassevich commented on XERCESJ-1740: --- I see this more of a req

[jira] [Resolved] (XERCESJ-1739) EntityResolver is not invoked for xsi:schemaLocation attribute

[ https://issues.apache.org/jira/browse/XERCESJ-1739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1739. --- Resolution: Invalid This is working as designed. The JAXP spec requires thi

[jira] [Closed] (XERCESJ-1734) Xerces does not correctly interpret negative jaxp processing limits as "NO LIMIT"

[ https://issues.apache.org/jira/browse/XERCESJ-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich closed XERCESJ-1734. - > Xerces does not correctly interpret negative jaxp processing limits as "NO > LIM

[jira] [Resolved] (XERCESJ-1734) Xerces does not correctly interpret negative jaxp processing limits as "NO LIMIT"

[ https://issues.apache.org/jira/browse/XERCESJ-1734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1734. --- Resolution: Invalid The class and functionality that you are referring to d

[jira] [Issue Comment Deleted] (XERCESJ-294) ID/IDREF validation failure: not enough info in error message

[ https://issues.apache.org/jira/browse/XERCESJ-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-294: - Comment: was deleted (was: oke finish) > ID/IDREF validation failure: not enoug

[jira] [Issue Comment Deleted] (XERCESJ-793) When using serializer in 'content handler' mode, duplicate namespace delcarations are missed

[ https://issues.apache.org/jira/browse/XERCESJ-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-793: - Comment: was deleted (was: oke finish) > When using serializer in 'content hand

[jira] [Issue Comment Deleted] (XERCESJ-493) Xerces 2.2.0 - 1.4.4 incompatibility

[ https://issues.apache.org/jira/browse/XERCESJ-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-493: - Comment: was deleted (was: oke finish) > Xerces 2.2.0 - 1.4.4 incompatibility >

[jira] [Commented] (XERCESJ-1592) schema validation incorrectly treating single character outside of BMP as two characters

[ https://issues.apache.org/jira/browse/XERCESJ-1592?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17343495#comment-17343495 ] Michael Glavassevich commented on XERCESJ-1592: --- You should ask your ques

[jira] [Commented] (XERCESJ-1703) Can't get validation examples to work with XSD 1.1

[ https://issues.apache.org/jira/browse/XERCESJ-1703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16916905#comment-16916905 ] Michael Glavassevich commented on XERCESJ-1703: --- There have been many JIR

[jira] [Commented] (XERCESJ-1681) Report parse error when element names begin with "xml"

[ https://issues.apache.org/jira/browse/XERCESJ-1681?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16914386#comment-16914386 ] Michael Glavassevich commented on XERCESJ-1681: --- Agreed this is not an er

[jira] [Updated] (XERCESJ-793) When using serializer in 'content handler' mode, duplicate namespace delcarations are missed

[ https://issues.apache.org/jira/browse/XERCESJ-793?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-793: - Attachment: (was: pdi-Exam-Dumps-2019.pdf) > When using serializer in 'conte

[jira] [Updated] (XERCESJ-294) ID/IDREF validation failure: not enough info in error message

[ https://issues.apache.org/jira/browse/XERCESJ-294?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-294: - Attachment: (was: marketing-cloud-email-specialist-Exam-Dumps-2019.pdf) > ID

[jira] [Updated] (XERCESJ-493) Xerces 2.2.0 - 1.4.4 incompatibility

[ https://issues.apache.org/jira/browse/XERCESJ-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-493: - Attachment: (was: pdii-Exam-Dumps-2019.pdf) > Xerces 2.2.0 - 1.4.4 incompati

[jira] [Comment Edited] (XERCESJ-1695) Xerces2J v 2.12 not available on Maven Central

[ https://issues.apache.org/jira/browse/XERCESJ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517259#comment-16517259 ] Michael Glavassevich edited comment on XERCESJ-1695 at 6/19/18 4:00 PM: -

[jira] [Commented] (XERCESJ-1695) Xerces2J v 2.12 not available on Maven Central

[ https://issues.apache.org/jira/browse/XERCESJ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16517259#comment-16517259 ] Michael Glavassevich commented on XERCESJ-1695: --- That was the goal but I

[jira] [Resolved] (XERCESJ-1697) CLONE - XercesImpl 2.12.0 is not available on maven central - Manually upload new jar

[ https://issues.apache.org/jira/browse/XERCESJ-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1697. --- Resolution: Duplicate You're making the same request as the opener of XERCE

[jira] [Closed] (XERCESJ-1697) CLONE - XercesImpl 2.12.0 is not available on maven central - Manually upload new jar

[ https://issues.apache.org/jira/browse/XERCESJ-1697?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich closed XERCESJ-1697. - > CLONE - XercesImpl 2.12.0 is not available on maven central - Manually upload >

[jira] [Commented] (XERCESJ-1695) Xerces2J v 2.12 not available on Maven Central

[ https://issues.apache.org/jira/browse/XERCESJ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16515840#comment-16515840 ] Michael Glavassevich commented on XERCESJ-1695: --- Yes, someone could manua

[jira] [Resolved] (XERCESJ-1696) XercesImpl 2.12.0 is not available on maven central

[ https://issues.apache.org/jira/browse/XERCESJ-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1696. --- Resolution: Duplicate > XercesImpl 2.12.0 is not available on maven central

[jira] [Closed] (XERCESJ-1696) XercesImpl 2.12.0 is not available on maven central

[ https://issues.apache.org/jira/browse/XERCESJ-1696?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich closed XERCESJ-1696. - > XercesImpl 2.12.0 is not available on maven central > ---

[jira] [Comment Edited] (XERCESJ-1695) Xerces2J v 2.12 not available on Maven Central

[ https://issues.apache.org/jira/browse/XERCESJ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495328#comment-16495328 ] Michael Glavassevich edited comment on XERCESJ-1695 at 5/30/18 3:43 PM: -

[jira] [Comment Edited] (XERCESJ-1695) Xerces2J v 2.12 not available on Maven Central

[ https://issues.apache.org/jira/browse/XERCESJ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495328#comment-16495328 ] Michael Glavassevich edited comment on XERCESJ-1695 at 5/30/18 3:39 PM: -

[jira] [Commented] (XERCESJ-1695) Xerces2J v 2.12 not available on Maven Central

[ https://issues.apache.org/jira/browse/XERCESJ-1695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16495328#comment-16495328 ] Michael Glavassevich commented on XERCESJ-1695: --- There's was a discussion

[jira] [Commented] (XERCESJ-1692) Inconsistent method name

[ https://issues.apache.org/jira/browse/XERCESJ-1692?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16461189#comment-16461189 ] Michael Glavassevich commented on XERCESJ-1692: --- Changing the name of a pu

[jira] [Comment Edited] (XERCESJ-1690) XMLUtils.isNameStart does not recognize valid characters

[ https://issues.apache.org/jira/browse/XERCESJ-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364594#comment-16364594 ] Michael Glavassevich edited comment on XERCESJ-1690 at 2/14/18 6:47 PM: --

[jira] [Comment Edited] (XERCESJ-1690) XMLUtils.isNameStart does not recognize valid characters

[ https://issues.apache.org/jira/browse/XERCESJ-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364594#comment-16364594 ] Michael Glavassevich edited comment on XERCESJ-1690 at 2/14/18 6:46 PM: --

[jira] [Commented] (XERCESJ-1690) XMLUtils.isNameStart does not recognize valid characters

[ https://issues.apache.org/jira/browse/XERCESJ-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16364594#comment-16364594 ] Michael Glavassevich commented on XERCESJ-1690: --- The answer hasn't changed

[jira] [Resolved] (XERCESJ-1690) XMLUtils.isNameStart does not recognize valid characters

[ https://issues.apache.org/jira/browse/XERCESJ-1690?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1690. --- Resolution: Not A Problem This is not a defect. Xerces supports XML 1.0 4th

[jira] [Comment Edited] (XERCESJ-1687) XSD 1.1 validation with xs:assert is not thread safe

[ https://issues.apache.org/jira/browse/XERCESJ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273378#comment-16273378 ] Michael Glavassevich edited comment on XERCESJ-1687 at 11/30/17 8:41 PM: -

[jira] [Comment Edited] (XERCESJ-1687) XSD 1.1 validation with xs:assert is not thread safe

[ https://issues.apache.org/jira/browse/XERCESJ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273378#comment-16273378 ] Michael Glavassevich edited comment on XERCESJ-1687 at 11/30/17 8:40 PM: -

[jira] [Commented] (XERCESJ-1687) XSD 1.1 validation with xs:assert is not thread safe

[ https://issues.apache.org/jira/browse/XERCESJ-1687?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16273378#comment-16273378 ] Michael Glavassevich commented on XERCESJ-1687: --- Until there's a fix to th

[jira] [Resolved] (XERCESJ-1686) Very high memory usage validating XSD 1.1 (+memory leak)

[ https://issues.apache.org/jira/browse/XERCESJ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1686. --- Resolution: Duplicate If you have something to add, please comment on the ex

[jira] [Closed] (XERCESJ-1686) Very high memory usage validating XSD 1.1 (+memory leak)

[ https://issues.apache.org/jira/browse/XERCESJ-1686?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich closed XERCESJ-1686. - > Very high memory usage validating XSD 1.1 (+memory leak) > ---

[jira] [Resolved] (XERCESJ-1547) Huge CPU comsumption when parsing elements with attributes hashing to the same value

[ https://issues.apache.org/jira/browse/XERCESJ-1547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1547. --- Resolution: Fixed Patches have been available for this issue since 2012. See

[jira] [Resolved] (XERCESJ-1685) Security threat CVE-2012-0881

[ https://issues.apache.org/jira/browse/XERCESJ-1685?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1685. --- Resolution: Fixed Patches have been available for this issue since 2012. See

[jira] [Resolved] (XERCESJ-1679) xercesImpl: Security threat CVE-2013-4002

[ https://issues.apache.org/jira/browse/XERCESJ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1679. --- Resolution: Fixed This issue has already been fixed. If you require a patch

[jira] [Updated] (XERCESJ-1679) xercesImpl: Security threat CVE-2013-4002

[ https://issues.apache.org/jira/browse/XERCESJ-1679?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1679: -- Fix Version/s: 2.12.0 > xercesImpl: Security threat CVE-2013-4002 > --

[jira] [Commented] (XERCESJ-589) Bug with pattern restriction on long strings

[ https://issues.apache.org/jira/browse/XERCESJ-589?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15305172#comment-15305172 ] Michael Glavassevich commented on XERCESJ-589: -- com.sun.org.apache.xerces.in

[jira] [Updated] (XERCESJ-1540) getParticle() method of XSComplexTypeDefinition, does not return element references in a complex type

[ https://issues.apache.org/jira/browse/XERCESJ-1540?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1540: -- Fix Version/s: (was: 2.11.0) > getParticle() method of XSComplexTypeDefini

[jira] [Updated] (XERCESJ-1660) Xerces error messages in French

[ https://issues.apache.org/jira/browse/XERCESJ-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1660: -- Fix Version/s: (was: 2.11.0) > Xerces error messages in French > -

[jira] [Updated] (XERCESJ-1648) Value of ID-type attribute not properly validated with respect to XML Schema 1.1 specification

[ https://issues.apache.org/jira/browse/XERCESJ-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1648: -- Fix Version/s: (was: 2.11.0) > Value of ID-type attribute not properly val

[jira] [Updated] (XERCESJ-1660) Xerces error messages in French

[ https://issues.apache.org/jira/browse/XERCESJ-1660?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1660: -- Affects Version/s: 2.11.0 > Xerces error messages in French >

[jira] [Updated] (XERCESJ-1648) Value of ID-type attribute not properly validated with respect to XML Schema 1.1 specification

[ https://issues.apache.org/jira/browse/XERCESJ-1648?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1648: -- Affects Version/s: 2.11.0 > Value of ID-type attribute not properly validated

[jira] [Updated] (XERCESJ-1635) Report warning when we have undeclared entity reference in XML content

[ https://issues.apache.org/jira/browse/XERCESJ-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1635: -- Fix Version/s: (was: 2.11.0) > Report warning when we have undeclared enti

[jira] [Updated] (XERCESJ-1635) Report warning when we have undeclared entity reference in XML content

[ https://issues.apache.org/jira/browse/XERCESJ-1635?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1635: -- Affects Version/s: 2.11.0 > Report warning when we have undeclared entity refe

[jira] [Updated] (XERCESJ-1634) Synchronization problem in XMLGrammarPoolImpl.

[ https://issues.apache.org/jira/browse/XERCESJ-1634?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1634: -- Fix Version/s: (was: 2.11.0) > Synchronization problem in XMLGrammarPoolIm

[jira] [Resolved] (XERCESJ-1666) java.lang.NoSuchFieldError: fRecognizedFeatures at org.apache.xerces.parsers.XML11Configuration.(Unknown Source)

[ https://issues.apache.org/jira/browse/XERCESJ-1666?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1666. --- Resolution: Invalid Such errors can only occur if you have multiple copies o

[jira] [Resolved] (XERCESJ-1667) ClassLoader memory leak via stacktrace in pre-created DOMNormalizer.abort exception

[ https://issues.apache.org/jira/browse/XERCESJ-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1667. --- Resolution: Fixed Also a funny thing... I wrote the original fix in Xerces.

[jira] [Assigned] (XERCESJ-1667) ClassLoader memory leak via stacktrace in pre-created DOMNormalizer.abort exception

[ https://issues.apache.org/jira/browse/XERCESJ-1667?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1667: - Assignee: Michael Glavassevich > ClassLoader memory leak via stacktrace

[jira] [Commented] (XERCESJ-1665) DTDGrammar.QNameHashtable.get(String key) compares by reference

[ https://issues.apache.org/jira/browse/XERCESJ-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14936792#comment-14936792 ] Michael Glavassevich commented on XERCESJ-1665: --- org.apache.xerces.impl.dt

[jira] [Resolved] (XERCESJ-1665) DTDGrammar.QNameHashtable.get(String key) compares by reference

[ https://issues.apache.org/jira/browse/XERCESJ-1665?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1665. --- Resolution: Invalid Working as designed. All XML string identifiers within X

[jira] [Commented] (XERCESJ-1102) Wrong value of xml:base attribute after resolving XInclude references

[ https://issues.apache.org/jira/browse/XERCESJ-1102?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14701729#comment-14701729 ] Michael Glavassevich commented on XERCESJ-1102: --- What Xerces needs most is

[jira] [Resolved] (XERCESJ-1659) JAXPSecureProcessingTest fails on non-English locales

[ https://issues.apache.org/jira/browse/XERCESJ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1659. --- Resolution: Fixed Matthias, thanks for the patch. Just committed it. It's in

[jira] [Assigned] (XERCESJ-1659) JAXPSecureProcessingTest fails on non-English locales

[ https://issues.apache.org/jira/browse/XERCESJ-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1659: - Assignee: Michael Glavassevich > JAXPSecureProcessingTest fails on non-

[jira] [Resolved] (XERCESJ-1656) access to portal layout

[ https://issues.apache.org/jira/browse/XERCESJ-1656?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1656. --- Resolution: Invalid This doesn't seem to have anything to do with Xerces. >

[jira] [Commented] (XERCESJ-911) Traversing the DOM throws NullPointerException

[ https://issues.apache.org/jira/browse/XERCESJ-911?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14365609#comment-14365609 ] Michael Glavassevich commented on XERCESJ-911: -- Here's a pointer to a rather

[jira] [Commented] (XERCESJ-1654) Add support for properties set by JAXP in the JDK (secure-processing, accessExternalDTD and entityExpansionLimit)

[ https://issues.apache.org/jira/browse/XERCESJ-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14349000#comment-14349000 ] Michael Glavassevich commented on XERCESJ-1654: --- This is a feature request

[jira] [Updated] (XERCESJ-1654) Add support for properties set by JAXP in the JDK (secure-processing, accessExternalDTD and entityExpansionLimit)

[ https://issues.apache.org/jira/browse/XERCESJ-1654?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1654: -- Issue Type: New Feature (was: Bug) > Add support for properties set by JAXP i

[jira] [Resolved] (XERCESJ-1651) Patterns containing \w and/or \W are not processed correctly.

[ https://issues.apache.org/jira/browse/XERCESJ-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1651. --- Resolution: Fixed Fixed. See SVN revision 1638344. > Patterns containing \w

[jira] [Assigned] (XERCESJ-1651) Patterns containing \w and/or \W are not processed correctly.

[ https://issues.apache.org/jira/browse/XERCESJ-1651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1651: - Assignee: Michael Glavassevich > Patterns containing \w and/or \W are n

[jira] [Created] (XERCESJ-1651) Patterns containing \w and/or \W are not processed correctly.

Michael Glavassevich created XERCESJ-1651: - Summary: Patterns containing \w and/or \W are not processed correctly. Key: XERCESJ-1651 URL: https://issues.apache.org/jira/browse/XERCESJ-1651 Pro

[jira] [Comment Edited] (XERCESJ-1646) Report warning when the maxLength limit is exceeded in an enumeration

[ https://issues.apache.org/jira/browse/XERCESJ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158035#comment-14158035 ] Michael Glavassevich edited comment on XERCESJ-1646 at 10/3/14 2:29 PM: --

[jira] [Commented] (XERCESJ-1646) Report warning when the maxLength limit is exceeded in an enumeration

[ https://issues.apache.org/jira/browse/XERCESJ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14158035#comment-14158035 ] Michael Glavassevich commented on XERCESJ-1646: --- At most this is a warning

[jira] [Updated] (XERCESJ-1646) Report warning when the maxLength limit is exceeded in an enumeration

[ https://issues.apache.org/jira/browse/XERCESJ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1646: -- Component/s: XML Schema 1.0 Datatypes Summary: Report warning when the

[jira] [Updated] (XERCESJ-1646) Error not reported when the maxLength limit is exceeded in an enumeration

[ https://issues.apache.org/jira/browse/XERCESJ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1646: -- Issue Type: Improvement (was: Bug) > Error not reported when the maxLength li

[jira] [Comment Edited] (XERCESJ-1646) Error not reported when the maxLength limit is exceeded in an enumeration

[ https://issues.apache.org/jira/browse/XERCESJ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156637#comment-14156637 ] Michael Glavassevich edited comment on XERCESJ-1646 at 10/2/14 2:58 PM: --

[jira] [Commented] (XERCESJ-1646) Error not reported when the maxLength limit is exceeded in an enumeration

[ https://issues.apache.org/jira/browse/XERCESJ-1646?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14156637#comment-14156637 ] Michael Glavassevich commented on XERCESJ-1646: --- It's been a long time sin

[jira] [Assigned] (XERCESJ-1641) totalEntitySizeLimit system property

[ https://issues.apache.org/jira/browse/XERCESJ-1641?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1641: - Assignee: Michael Glavassevich > totalEntitySizeLimit system property >

[jira] [Assigned] (XERCESJ-1642) Make SecureProcessingConfiguration the default

[ https://issues.apache.org/jira/browse/XERCESJ-1642?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1642: - Assignee: Michael Glavassevich > Make SecureProcessingConfiguration the

[jira] [Resolved] (XERCESJ-1644) RFE: Allow global enabling/disabling of features with secure defaults

[ https://issues.apache.org/jira/browse/XERCESJ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1644. --- Resolution: Duplicate Function is covered by the SecureProcessingConfigurat

[jira] [Commented] (XERCESJ-1644) RFE: Allow global enabling/disabling of features with secure defaults

[ https://issues.apache.org/jira/browse/XERCESJ-1644?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14106940#comment-14106940 ] Michael Glavassevich commented on XERCESJ-1644: --- Hi, I'm guessing neither

[jira] [Resolved] (XERCESJ-1637) Improvement: Remove dead code in IteratorView sample

[ https://issues.apache.org/jira/browse/XERCESJ-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1637. --- Resolution: Fixed Thanks Elliotte. I've committed your patch to SVN. > Imp

[jira] [Updated] (XERCESJ-1640) Regex in asserts fails to validate.

[ https://issues.apache.org/jira/browse/XERCESJ-1640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1640: -- Component/s: XML Schema 1.1 Structures XML Schema 1.1 Datatyp

[jira] [Resolved] (XERCESJ-1639) Adding assertions in an abstract complex type

[ https://issues.apache.org/jira/browse/XERCESJ-1639?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1639. --- Resolution: Not a Problem This is not a bug report. Please use the user mai

[jira] [Closed] (XERCESJ-1638) Java Null Pointer Exception when calling from JAXB Unmarshal Function

[ https://issues.apache.org/jira/browse/XERCESJ-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich closed XERCESJ-1638. - Not an Apache issue. > Java Null Pointer Exception when calling from JAXB Unmarsha

[jira] [Resolved] (XERCESJ-1638) Java Null Pointer Exception when calling from JAXB Unmarshal Function

[ https://issues.apache.org/jira/browse/XERCESJ-1638?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1638. --- Resolution: Invalid Classes in com.sun.xml.internal.* and com.sun.org.apach

[jira] [Updated] (XERCESJ-1637) dead code in IteratorView

[ https://issues.apache.org/jira/browse/XERCESJ-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1637: -- Component/s: Samples > dead code in IteratorView > -

[jira] [Updated] (XERCESJ-1637) Improvement: Remove dead code in IteratorView sample

[ https://issues.apache.org/jira/browse/XERCESJ-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1637: -- Summary: Improvement: Remove dead code in IteratorView sample (was: dead cod

[jira] [Assigned] (XERCESJ-1637) dead code in IteratorView

[ https://issues.apache.org/jira/browse/XERCESJ-1637?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1637: - Assignee: Michael Glavassevich > dead code in IteratorView > --

[jira] [Updated] (XERCESJ-1624) Wrong namespace binding used for resolving QName prefix in an XSD

[ https://issues.apache.org/jira/browse/XERCESJ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1624: -- Summary: Wrong namespace binding used for resolving QName prefix in an XSD (

[jira] [Assigned] (XERCESJ-1624) Wrong namespace binding used for resolving QName prefix in an XSD

[ https://issues.apache.org/jira/browse/XERCESJ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich reassigned XERCESJ-1624: - Assignee: Michael Glavassevich > Wrong namespace binding used for resol

[jira] [Updated] (XERCESJ-1624) Wrong namepsace binding used for resolving QName prefix in an XSD

[ https://issues.apache.org/jira/browse/XERCESJ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1624: -- Summary: Wrong namepsace binding used for resolving QName prefix in an XSD (

[jira] [Updated] (XERCESJ-1624) Element

[ https://issues.apache.org/jira/browse/XERCESJ-1624?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1624: -- Component/s: XML Schema 1.0 Structures > Element > --- > >

[jira] [Resolved] (XERCESJ-1631) Testing Xerces security Manager maxOccurNodeLimit

[ https://issues.apache.org/jira/browse/XERCESJ-1631?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich resolved XERCESJ-1631. --- Resolution: Not A Problem SecurityManger.setMaxOccurNodeLimit() specifies a

[jira] [Updated] (XERCESJ-1558) GSoC: Implement the StAX XMLStreamWriter

[ https://issues.apache.org/jira/browse/XERCESJ-1558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1558: -- Labels: gsoc gsoc2014 mentor (was: gsoc gsoc2013 mentor) > GSoC: Implement t

[jira] [Updated] (XERCESJ-1227) Poor performance / OutOfMemoryError for sequences, choices and nested with large minOccurs/maxOccurs

[ https://issues.apache.org/jira/browse/XERCESJ-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1227: -- Description: We now handle large minOccurs/maxOccurs on element/wildcard part

[jira] [Updated] (XERCESJ-1227) Poor performance / OutOfMemoryError for sequences, choices and nested with large minOccurs/maxOccurs

[ https://issues.apache.org/jira/browse/XERCESJ-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1227: -- Labels: gsoc gsoc2014 mentor (was: gsoc gsoc2013 mentor) > Poor performance

[jira] [Updated] (XERCESJ-1227) Poor performance / OutOfMemoryError for sequences, choices and nested with large minOccurs/maxOccurs

[ https://issues.apache.org/jira/browse/XERCESJ-1227?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Glavassevich updated XERCESJ-1227: -- Component/s: XML Schema 1.1 Structures > Poor performance / OutOfMemoryError

  1   2   3   4   5   6   7   8   9   10   >