DO NOT REPLY [Bug 40897] String comparisons using '==' causes validation errors with some parsers

[bu...@apache.org]

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





--- Comment #4 from Raul Benito <ra...@r-bg.com>  2008-05-09 08:00:53 PST ---
(In reply to comment #3)
> Can this be a case of "the flawed microbenchmark".  (google it).  .equals is
> slower but on the whole operation (signing, encryption, etc) the XML time is
> mostly spent on parsing and serialization I would guess.  And I'm skipping the
> cryptographic primitives...
> 
> I wonder what the test case is.
> 

I have do a lot of benchamark and really this is a huge improve. I can tell you
why but it will be a big post. And I have do my exercises, and i benchmark the
whole operation. Anyway 2 releases ago it was plain impossible to use another
parser than xerces (and really a concrete one), we have improve it til the way
that now, only this is possible and works with different ones that intern
namespaces. 

Anyway i think that sadly for a fully spec compliant there is no other options
than a special xalan+xerces (for xpath transformations).

But I still that if a parser doesn't intern namespaces will be hit by a lot of
just a difference in the end, that happens with versioning in xml. I just
create the patch in order to disable the NS comparison.





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