Mailing-List: contact issues-help@commons.apache.org; run by ezmlm
Precedence: bulk
Reply-To: issues@commons.apache.org
Message-ID: <736301396.1213228725034.JavaMail.jira@brutus>
Date: Wed, 11 Jun 2008 16:58:45 -0700 (PDT)
From: "Matt Benson (JIRA)" <jira@apache.org>
To: issues@commons.apache.org
Subject: [jira] Resolved: (JXPATH-123) Regression:  "fix" made to
 NamespaceResolver broke existing testcases
In-Reply-To: <617693414.1213228245148.JavaMail.jira@brutus>
MIME-Version: 1.0
Content-Type: text/plain; charset=utf-8
Content-Transfer-Encoding: 7bit


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

Matt Benson resolved JXPATH-123.
--------------------------------

    Resolution: Fixed

svn rev 666910

> Regression:  "fix" made to NamespaceResolver broke existing testcases
> ---------------------------------------------------------------------
>
>                 Key: JXPATH-123
>                 URL: https://issues.apache.org/jira/browse/JXPATH-123
>             Project: Commons JXPath
>          Issue Type: Bug
>    Affects Versions: 1.2 Final
>            Reporter: Matt Benson
>             Fix For: 1.3
>
>
> Relatively shortly after introducing NamespaceResolver, Dmitri had changed it to wipe out the reverse mapping cache every time a new mapping was added.  The tests, however, relied upon the last added mapping to a given namespace being the preferred prefix.  The description for his change was that he was fixing a "bug", but since he didn't elaborate on what kind of bug I can't see how maintaining the cache is any more harmful than not maintaining it, and reverting this change clears up the test failures that for some reason are only seen on JDK 1.3.

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