You are viewing a plain text version of this content. The canonical link for it is here.
Posted to j-dev@xerces.apache.org by bu...@apache.org on 2004/03/30 20:56:35 UTC

DO NOT REPLY [Bug 28061] New: - TypeInfo.isDerivedFrom ignores derivationMode parameter

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28061>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28061

TypeInfo.isDerivedFrom ignores derivationMode parameter

           Summary: TypeInfo.isDerivedFrom ignores derivationMode parameter
           Product: Xerces2-J
           Version: 2.6.2
          Platform: All
        OS/Version: All
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: DOM
        AssignedTo: xerces-j-dev@xml.apache.org
        ReportedBy: carnold@houston.rr.com


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.

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