xerces-j-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From xerces-j-...@xml.apache.org
Subject [jira] Resolved: (XERCESJ-938) TypeInfo.isDerivedFrom ignores derivationMode parameter
Date Mon, 27 Sep 2004 18:17:35 GMT
Message:

   The following issue has been resolved as FIXED.

   Resolver: nddelima
       Date: Mon, 27 Sep 2004 11:16 AM

Hi Curt,

The methods derivedFromType and derivedFrom are defined in the XML Schema Component API [1]
and should preferably not be removed or changed.  Unfortunately differences exist between
specified behavior of XSTypeDefinition.derivedFrom[2] and TypeInfo.isDerivedFrom[3].  Though
previous implementations of methods derivedFrom and derivedFromType should be bypassed, they
should not be replaced with something new.  I have a applied a functionally equivalent patch.
 All W3C's DOM L3 Core tests but typeinfoisderivedfrom73 pass.  

Thanks,
Neil.

[1] http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040309/
[2] http://www.w3.org/Submission/2004/SUBM-xmlschema-api-20040309/xml-schema-api.html#XSTypeDefinition-derivedFrom
[3] http://www.w3.org/TR/2004/REC-DOM-Level-3-Core-20040407/core.html#TypeInfo-isDerivedFrom
---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/XERCESJ-938

Here is an overview of the issue:
---------------------------------------------------------------------
        Key: XERCESJ-938
    Summary: TypeInfo.isDerivedFrom ignores derivationMode parameter
       Type: Bug

     Status: Resolved
 Resolution: FIXED

    Project: Xerces2-J
 Components: 
             DOM
   Versions:
             2.6.2

   Assignee: 
   Reporter: Curt Arnold

    Created: Tue, 30 Mar 2004 6:56 PM
    Updated: Mon, 27 Sep 2004 11:16 AM
Environment: Operating System: All
Platform: All

Description:
Per a request from Neil Delima:

The current implementation of TypeInfo.isDerivedFrom will fail a large 
fraction of the related DOM test suite tests.  The attached patch will pass 
all but one (typeinfoisderivedfrom73).

This code bypasses the previous derivedFromType and derivedFrom methods which 
should either be removed or deprecated.

typeinfoisderivedfrom73 fails due to the expansion of union of union types.  
If you have T1 is a union of T2 and T3 and T3 is a union of T4 and T5, the 
member types of T1 will contain T2, T4 and T5 as if T3 did not exist.  ...73 
basically asks if T1 derives from T3 which it expected to return true.


---------------------------------------------------------------------
JIRA INFORMATION:
This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa

If you want more information on JIRA, or have a bug to report see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: xerces-j-dev-unsubscribe@xml.apache.org
For additional commands, e-mail: xerces-j-dev-help@xml.apache.org


Mime
View raw message