Okay, I'll prepare a patch for you by the end of the week.
On 8/24/10 2:23 PM, Colm O hEigeartaigh wrote:
Sounds fine to me.
Colm.
On Mon, Aug 23, 2010 at 8:55 PM, Chad La Joie wrote:
Okay, getting back to this.
I tried my tests again this time with:
- a 7.5MB SAML metadata documen
I'll add my 10c to the detail discussion.
On 10/08/10 01:23, Chad La Joie wrote:
> Not necessarily, there are a number of not equal checks in there that
> should, in theory, perform better if you only use == only. In such a
> case, the use of != will just be a single check whi
mparison as the default for the next release, given that
there is no compelling reason to do otherwise. Anyone who wants to
experiment with getting a performance increase, can just plug the
other piece of code in.
Thoughts?
Colm.
On Mon, Aug 9, 2010 at 11:07 PM, Chad La
ted
problem I'll add my 10c to the detail discussion.
On 10/08/10 01:23, Chad La Joie wrote:
> Not necessarily, there are a number of not equal checks in there that
> should, in theory, perform better if you only use == only. In such a
> case, the use of != wil
a lot
nicer to read.
On 8/9/10 10:19 AM, Chad La Joie wrote:
So, I have some unexpected results from this work.
I implemented a helper class that checked the equality of element local
names, attribute local names, namespace URIs, and namespace prefixes
(i.e. everything that Xerces always intern
String.equals() with an overwhelming
percentage of equal strings?
I'd have to look at exactly where all calls occur, it's possible but if
my memory is currently serving me well, it's not the case.
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
running out of memory?
Those test files should produce anything that would use up the default
amount of memory.
I'm using Apple's repackage of Sun JDK 1.6.0_20, 64 bit
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
On 8/9/10 10:45 AM, Chad La Joie wrote:
My testings were more reliable if use 100 warms-up let the jit run its
magic, and then go for the timed test.
Okay, I try that.
It made no difference.
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
, the
second will be handicap, as the first one will be just inline the second
will have a switch to see if it is one interface or the other.
No, each run was in a clean JVM.
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
on=350494&view=markup
[3]
http://svn.apache.org/viewvc/xml/security/trunk/data/org/apache/xml/security/c14n/inExcl/example2_2_3.xml?revision=350915&view=markup
On 8/2/10 10:11 AM, Chad La Joie wrote:
So, while I don't have my access yet, Colm asked me if I'd take a look
at the ==
it will be
removed.
Validated with xmllint --noout --schema example.xsd example.xml
Is this really correct for this canonicalization method to damage the xml file?
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
and mark ElementChecker as deprecated. Then it can
be removed later.
--
Chad La Joie
www.itumi.biz
trusted identities, delivered
nt.
No, no account (that I know of) yet. :(
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
gi?id=46681
[4] https://issues.apache.org/bugzilla/show_bug.cgi?id=45637#c1
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
h the JRE.
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
ey resolution method was added to the KeyResolver I'd
recommend moving the construction of the KEK resolver to a method
anyways. Given some of the complexities surrounding key resolution
within XML encryption it's certainly not hard to imagine some else down
the road will need a hoo
n the Shibboleth
and OpenSAML projects on the Java side as the main architect there, and he's
been doing some new work on top of the JSR105 code and may be in a position
to fix some bugs or make suggestions.
-- Scott
--
Chad La Joie
http://itumi.biz
trusted identities, delivered
Attached are a set of patches and a new class that allows the CVS HEAD
code to compile on JDK 1.3. The TransformXPath and XMLSignatureInput
classes were throwing runtime exceptions and were chaining the causal
exceptions. I created an XMLSecurityRuntimeException which behaves
exactly like XMLSecu
18 matches
Mail list logo