axis-java-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
Subject [jira] Assigned: (AXIS-1304) DefaultEntityResolver is broken
Date Sun, 06 Jun 2004 05:56:54 GMT

   The following issue has been re-assigned.

   Assignee: Davanum Srinivas (
View the issue:

Here is an overview of the issue:
        Key: AXIS-1304
    Summary: DefaultEntityResolver is broken
       Type: Bug

     Status: Open
   Priority: Major

    Project: Axis
             WSDL processing
             current (nightly)

   Assignee: Davanum Srinivas
   Reporter: Joseph Dane

    Created: Mon, 12 Apr 2004 5:53 PM
    Updated: Sat, 5 Jun 2004 10:56 PM

in XMLUtils.newDocument(InputSource), the parser has an entity resolver set using
DefaultEntityResolver.  This resolver just returns an empty input source for all inputs.

As I read the javadocs for EntityResolver, this is wrong.  The resolver can (should?) also
choose to return null, indicating that the parser should open a regular URI connection to
the resource.

how did this come up?  in an attempt to improve on some fairly awful xerces performance, I
tried to setup my webapp to use resin's XML/XSL implementation.  As it turns out, resin's
XML parser tries to use its EntityResolver to lookup the document itself, which I think is
also incorrect.  The DefaultEntityResolver implementation causes this to fail.

Again, as I read the javadocs, resin should not be doing this, and I'll be reporting a bug
there as well.  But ISTM that a DefaultEntityResovler that always returns null makes as much
sense as one that always returns an empty stream.

This message is automatically generated by JIRA.

If you think it was sent incorrectly contact one of the administrators:

If you want more information on JIRA, or have a bug to report see:

View raw message