OpenSAML user discussion

["Douglas Squirrel" <>]

Thanks Scott. I replaced xmlsec-20050514.jar with the equivalent jar
from xmlsec 1.4.1 and tried to rebuild, but opensaml died in the
POSTProfile unit test - I guess at least this means I was successful in
replacing it! I will have a further look at what is causing the failure.

It looks like the bug you refer to is
http://issues.apache.org/bugzilla/show_bug.cgi?id=36532 and they do
indeed claim to have fixed it long since. Do you happen to know which
version of xmlsecurity the current jar (xmlsec-20050514.jar) is? Perhaps
I should just try version 1.3 or 1.4 instead of jumping all the way to
1.4.1.

-----Original Message-----
From: Scott Cantor 
[mailto:]
 
Sent: 31 July 2007 23:20
To: 

Subject: RE: Xerces 2.8.1 and Xalan 2.7.0 with OpenSAML 1.1

> What is very odd is that I can't see any reference to
> org.apache.xpath.compiler.FuncLoader - in this line, or anywhere else
in
> SAMLConfig.java, or in the Init class of org.apache.xml.security!

xml-security is at fault here. I long since last track of when or
whether
they fixed this bug, my brain dumped all of its Java neurons once I
moved to
C++ only. I thought it was fixed a long time ago though.

> I also tried replacing the versions of Xerces and Xalan in the
opensaml
> endorsed folder and rebuilding, as well as replacing
xmlsec-20050514.jar
> in the lib folder with a newer version, but nothing seemed to work.

If replacing xmlsec doesn't work, I don't have an answer for you, but I
think you're not actually replacing it. Pretty sure we're using Xalan
2.7 in
the 2.0 tree, and it would fail the same way.

If you find that opensaml itself can't run with xmlsec 1.4.1, I'll
accept
any patches, other than that the code is really frozen now.
 
-- Scott



______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________

______________________________________________________________________
This email has been scanned by the MessageLabs Email Security System.
For more information please visit http://www.messagelabs.com/email 
______________________________________________________________________