[ 
https://issues.apache.org/jira/browse/XERCESJ-1670?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Tobin Stelling updated XERCESJ-1670:
------------------------------------
    Description: 
This ticket is a request to incorporate the fix for XERCESJ-1591 into the 
2.12.0 release of Xerces. Please refer to XERCESJ-1591 for detailed information 
about the bug and its fix.

Attached is a svn generated patch that can be applied by entering trunk/ and 
running "svn patch <name>." The patch includes the fix currently checked into 
the xml-schema-1.1-dev branch (r1396551) as well as a new test. The test is in 
a new package under tests/ (schema.redefine). There might be a more appropriate 
place for it. The test walks through the example described in XERCESJ-1591 and 
asserts the correct error is returned by the parser (i.e., that the ID 
attribute is required for element 'el').

I'm submitting this ticket at the behest of David Costanzo who has already 
contacted the Xerces group regarding this bug.

I also believe https://www.w3.org/TR/xmlschema11-1/#modify-schema, "This 
mechanism is intended to provide a declarative and modular approach to schema 
modification, with functionality no different except in scope from what would 
be achieved by wholesale text copying and redefinition by editing" shows that 
this is a bug.


  was:
This ticket is a request to incorporate the fix for XERCESJ-1591 into the 
2.12.0 release of Xerces. Please refer to XERCESJ-1591 for detailed information 
about the bug and its fix.

Attached is a svn generated patch that can be applied by entering trunk/ and 
running "svn patch <name>." The patch includes the fix currently checked into 
the xml-schema-1.1-dev branch (r1396551) as well as a new test. The test is in 
a new package under tests/ (schema.redefine). There might be a more appropriate 
place for it. The test walks through the example described in XERCESJ-1591 and 
asserts the correct error is returned by the parser (i.e., that the ID 
attribute is required for element 'el').

I'm submitting this ticket at the behest of David Costanzo who has already 
contacted the Xerces group regarding this bug.



> Cannot properly redefine attribute group which is not directly in the 
> redefined schema
> --------------------------------------------------------------------------------------
>
>                 Key: XERCESJ-1670
>                 URL: https://issues.apache.org/jira/browse/XERCESJ-1670
>             Project: Xerces2-J
>          Issue Type: Bug
>          Components: XML Schema 1.0 Datatypes
>    Affects Versions: 2.11.0
>            Reporter: Tobin Stelling
>         Attachments: XERCESJ-1591.diff
>
>
> This ticket is a request to incorporate the fix for XERCESJ-1591 into the 
> 2.12.0 release of Xerces. Please refer to XERCESJ-1591 for detailed 
> information about the bug and its fix.
> Attached is a svn generated patch that can be applied by entering trunk/ and 
> running "svn patch <name>." The patch includes the fix currently checked into 
> the xml-schema-1.1-dev branch (r1396551) as well as a new test. The test is 
> in a new package under tests/ (schema.redefine). There might be a more 
> appropriate place for it. The test walks through the example described in 
> XERCESJ-1591 and asserts the correct error is returned by the parser (i.e., 
> that the ID attribute is required for element 'el').
> I'm submitting this ticket at the behest of David Costanzo who has already 
> contacted the Xerces group regarding this bug.
> I also believe https://www.w3.org/TR/xmlschema11-1/#modify-schema, "This 
> mechanism is intended to provide a declarative and modular approach to schema 
> modification, with functionality no different except in scope from what would 
> be achieved by wholesale text copying and redefinition by editing" shows that 
> this is a bug.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to