Bug 45573 - ElementProxy uses == instead of .equals for namespace comparison
Summary: ElementProxy uses == instead of .equals for namespace comparison
Status: RESOLVED DUPLICATE of bug 40897
Alias: None
Product: Security - Now in JIRA
Classification: Unclassified
Component: Encryption (show other bugs)
Version: unspecified
Hardware: PC Windows XP
: P2 normal
Target Milestone: ---
Assignee: XML Security Developers Mailing List
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2008-08-05 20:39 UTC by Anli Shundi
Modified: 2008-08-15 11:51 UTC (History)
0 users


Attachments
patch replacing == with .equals (815 bytes, patch)
2008-08-05 20:39 UTC, Anli Shundi 		Details | Diff
View All Add an attachment (proposed patch, testcase, etc.)

Note You need to log in before you can comment on or make changes to this bug.
Description Anli Shundi 2008-08-05 20:39:04 UTC 
Created attachment 22393 [details]
patch replacing == with .equals
Comment 1 sean.mullan 2008-08-15 10:19:47 UTC 
See bug 40897. An extensible mechanism was added in 1.4.2 to allow you to
override the current implementation. See the org.apache.xml.security.utils.ElementChecker interface.

*** This bug has been marked as a duplicate of bug 40897 ***
Comment 2 Anli Shundi 2008-08-15 11:42:27 UTC 
Thanks... I should have remembered.  Then again the "extensibility mechanism" seems to require a recompile!  The following line in ElementProxy

   static ElementChecker checker = new ElementCheckerImpl.InternedNsChecker();

is executed unconditionally.  This is probably for a separate thread...
Comment 3 sean.mullan 2008-08-15 11:51:36 UTC 
(In reply to comment #2)
> Thanks... I should have remembered.  Then again the "extensibility mechanism"
> seems to require a recompile!  The following line in ElementProxy
> 
>    static ElementChecker checker = new ElementCheckerImpl.InternedNsChecker();
> 
> is executed unconditionally.  This is probably for a separate thread...
> 

Right, we need to add a new method or system property to allow you to set
your own ElementChecker. Can you open another issue?