[jira] Commented: (AXIS-1304) DefaultEntityResolver is broken

[ji...@apache.org]

The following comment has been added to this issue:

     Author: Joseph Dane
    Created: Tue, 13 Apr 2004 12:24 PM
       Body:
aha.  I suppose it is best to have Axis default to a safe behavior.  Still, wouldn't it
be better to let clients override this by providing their own resolver?  Maybe via
a configuration option?

---------------------------------------------------------------------
View this comment:
  http://issues.apache.org/jira/browse/AXIS-1304?page=comments#action_34998

---------------------------------------------------------------------
View the issue:
  http://issues.apache.org/jira/browse/AXIS-1304

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

     Status: Unassigned
   Priority: Major

    Project: Axis
 Components: 
             WSDL processing
   Versions:
             current (nightly)

   Assignee: 
   Reporter: Joseph Dane

    Created: Mon, 12 Apr 2004 5:53 PM
    Updated: Tue, 13 Apr 2004 12:24 PM

Description:
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.


---------------------------------------------------------------------
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