You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@santuario.apache.org by bu...@apache.org on 2008/08/06 05:39:05 UTC

DO NOT REPLY [Bug 45573] New: ElementProxy uses == instead of .equals for namespace comparison

https://issues.apache.org/bugzilla/show_bug.cgi?id=45573

           Summary: ElementProxy uses == instead of .equals for namespace
                    comparison
           Product: Security
           Version: unspecified
          Platform: PC
        OS/Version: Windows XP
            Status: NEW
          Severity: normal
          Priority: P2
         Component: Encryption
        AssignedTo: security-dev@xml.apache.org
        ReportedBy: ashundi@tibco.com


Created an attachment (id=22393)
 --> (https://issues.apache.org/bugzilla/attachment.cgi?id=22393)
patch replacing == with .equals


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

DO NOT REPLY [Bug 45573] ElementProxy uses == instead of .equals for namespace comparison

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45573





--- Comment #2 from Anli Shundi <as...@tibco.com>  2008-08-15 11:42:27 PST ---
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...


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

DO NOT REPLY [Bug 45573] ElementProxy uses == instead of .equals for namespace comparison

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45573





--- Comment #3 from sean.mullan@sun.com  2008-08-15 11:51:36 PST ---
(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?


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.

DO NOT REPLY [Bug 45573] ElementProxy uses == instead of .equals for namespace comparison

Posted by bu...@apache.org.
https://issues.apache.org/bugzilla/show_bug.cgi?id=45573


sean.mullan@sun.com changed:

           What    |Removed                     |Added
----------------------------------------------------------------------------
             Status|NEW                         |RESOLVED
         Resolution|                            |DUPLICATE




--- Comment #1 from sean.mullan@sun.com  2008-08-15 10:19:47 PST ---
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 ***


-- 
Configure bugmail: https://issues.apache.org/bugzilla/userprefs.cgi?tab=email
------- You are receiving this mail because: -------
You are the assignee for the bug.