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

["Dominik Kacprzak (JIRA)" <ax...@ws.apache.org>]

     [ http://nagoya.apache.org/jira/browse/AXIS-1304?page=comments#action_56524 ]
     
Dominik Kacprzak commented on AXIS-1304:
----------------------------------------

Forgot to mention that I successfully run 'all-tests' target with different settings for 'axis.SAXEntityResolverClas' property.

- Dominik

> DefaultEntityResolver is broken
> -------------------------------
>
>          Key: AXIS-1304
>          URL: http://nagoya.apache.org/jira/browse/AXIS-1304
>      Project: Axis
>         Type: Bug
>   Components: WSDL processing
>     Versions: current (nightly)
>     Reporter: Joseph Dane
>     Assignee: Davanum Srinivas
>  Attachments: AXIS-1304.tar.gz
>
> 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:
   http://nagoya.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