You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@commons.apache.org by "Rahul Akolkar (JIRA)" <ji...@apache.org> on 2008/12/23 07:19:44 UTC
[jira] Resolved: (DIGESTER-122) Use of null value if debug is
enabled in Digester.resolveEntity()
[ https://issues.apache.org/jira/browse/DIGESTER-122?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Rahul Akolkar resolved DIGESTER-122.
------------------------------------
Resolution: Fixed
Fix Version/s: 2.0
1.8.1
Thanks, this has been fixed in r728881:
http://svn.apache.org/viewvc?view=rev&revision=728881
> Use of null value if debug is enabled in Digester.resolveEntity()
> -----------------------------------------------------------------
>
> Key: DIGESTER-122
> URL: https://issues.apache.org/jira/browse/DIGESTER-122
> Project: Commons Digester
> Issue Type: Bug
> Affects Versions: 1.8
> Reporter: David Dillard
> Priority: Minor
> Fix For: 1.8.1, 2.0
>
>
> Here's the code:
> if (entityURL == null) {
> if (systemId == null) {
> // cannot resolve
> if (log.isDebugEnabled()) {
> log.debug(" Cannot resolve entity: '" + entityURL + "'");
> entityURL is known to be null and then it's used in the log message.
> This was detected by FindBugs.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.