This is an archived snapshot of W3C's public bugzilla bug tracker, decommissioned in April 2019. Please see the home page for more details.

Bug 442 - DOMEntityResolverTest0 is not effective
Summary: DOMEntityResolverTest0 is not effective
Status: RESOLVED FIXED
Alias: None
Product: DOM TS
Classification: Unclassified
Component: DOM Level 3 (show other bugs)
Version: unspecified
Hardware: Other other
: P2 normal
Target Milestone: ---
Assignee: Curt Arnold
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2003-12-18 19:02 UTC by Curt Arnold
Modified: 2003-12-19 00:54 UTC (History)
0 users

See Also:


Attachments
Fixes to DOMEntityResolverTest0 and added Test2 (7.32 KB, patch)
2003-12-18 19:04 UTC, Curt Arnold
Details
Fixes test validation errors in previous patch (2.16 KB, patch)
2003-12-18 19:54 UTC, Curt Arnold
Details

Description Curt Arnold 2003-12-18 19:02:32 UTC
DOMEntityResolverTest0 as originally written appeared to test the parameters 
on a call to resolveResource. The document being parsed did not have any 
external resources and resource resolvers do not participate in resolving the 
document entity, so resolveResource should not and was not invoked and the 
assertions were never evaluted.

I have rewritten DOMEntityResolverTest0 so that it parses a document with an 
external entity with an resource resolver.  The resourceResolver checks the 
parameters and replaces the external resource.  The test checks the document 
after parsing to check that the resolver was effective.

DOMEntityResolverTest2 was added to test that a resource resolver is not used 
to resolve the document entity.
Comment 1 Curt Arnold 2003-12-18 19:04:24 UTC
Created attachment 125 [details]
Fixes to DOMEntityResolverTest0 and added Test2
Comment 2 Curt Arnold 2003-12-18 19:54:48 UTC
Created attachment 126 [details]
Fixes test validation errors in previous patch