You are viewing a plain text version of this content. The canonical link for it is here.

Posted to dev@commons.apache.org by bu...@apache.org on 2004/04/20 08:05:14 UTC

DO NOT REPLY [Bug 28486] New: - [digester] ExtendedBaseRules test fails

DO NOT REPLY TO THIS EMAIL, BUT PLEASE POST YOUR BUG 
RELATED COMMENTS THROUGH THE WEB INTERFACE AVAILABLE AT
<http://issues.apache.org/bugzilla/show_bug.cgi?id=28486>.
ANY REPLY MADE TO THIS MESSAGE WILL NOT BE COLLECTED AND 
INSERTED IN THE BUG DATABASE.

http://issues.apache.org/bugzilla/show_bug.cgi?id=28486

[digester] ExtendedBaseRules test fails

           Summary: [digester] ExtendedBaseRules test fails
           Product: Commons
           Version: 1.5 Final
          Platform: All
        OS/Version: Other
            Status: NEW
          Severity: Normal
          Priority: Other
         Component: Digester
        AssignedTo: commons-dev@jakarta.apache.org
        ReportedBy: simon@ecnetwork.co.nz


When using the JDK1.2, "ant test.matching.extended" reports a failure in method
"testAncesterMatch".

I have added logging to the ExtendedBaseRules class, and the problem appears not
be with jdk1.2, but rather with the order objects are returned from the HashMap
rule cache. It seems that iterating over the entryset of elements in the cache
returns the elements in different order in the two JVMs, and somehow this seems
to break ExtendedBaseRules. It shouldn't, of course.

I'll continue to look into it, but would appreciate some help from those who are
familiar with this class, as the matching rules are *very* complex.

---------------------------------------------------------------------
To unsubscribe, e-mail: commons-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: commons-dev-help@jakarta.apache.org