[jira] Updated: (XMLCOMMONS-37) System.err.println statement should be removed

     [ https://issues.apache.org/jira/browse/XMLCOMMONS-37?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Michael Glavassevich updated XMLCOMMONS-37:
-------------------------------------------

    Affects Version/s:     (was: 1.x)
                       XML Commons Resolver 1.1.0

> System.err.println statement should be removed
> ----------------------------------------------
>
>                 Key: XMLCOMMONS-37
>                 URL: https://issues.apache.org/jira/browse/XMLCOMMONS-37
>             Project: XmlCommons
>          Issue Type: Bug
>          Components: XML Commons Resolver (resolver.jar)
>    Affects Versions: XML Commons Resolver 1.1.0
>         Environment: Operating System: other
> Platform: Other
>            Reporter: elharo
>            Assignee: Commons Developers Mailing List
>            Priority: Minor
>
> Libraries such as the Apache ResolvingXMLReader should not talk to the user. In
> particular they should not print things on System.err and Systsem.out unless
> speciifcally told to do so. The following fragment in CatalogManager.java is at
> issue:
> 	if (!ignoreMissingProperties) {
> 	  System.err.println("Cannot find "+propertyFile);
> 	  // there's no reason to give this warning more than once
> 	  ignoreMissingProperties = true;
> 	}
> I didn't call this class directly. My code used ResolvingXMLReader. Presumably
> ResolvingXMLReader called into CatalogManager somehow. In this case, if the
> XMLReader that is calling CatalogManager has a configured SAX ErrorHandler, then
> this message should be sent as a warning through that ErrorHandler by invoking
> its warning() method. If that XMLReader does not have such an ErrorHandler, then
> this message should be dropped.

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.