Closed GoogleCodeExporter closed 9 years ago
[deleted comment]
ok, looks like I have it working with xalan 2.7.0 if I change to openxri
version 1.0.1
and xmlsec version 1.4.1. Perhaps these should be updated in the openid4java
distribution.
Original comment by matt.ast...@gmail.com
on 15 Jan 2008 at 3:23
It may be due to the incompatibility between xalan 2.7.0 and xmlsec 1.3.0.
According
to this bug (http://issues.apache.org/bugzilla/show_bug.cgi?id=36532) it was
supposed
to be fixed for xmlsec-1.3.x but it seems that the OpenSAML folks had a related
incompatibility problem.
I wouldn't recommend upgrading to OpenXRI 1.0.1 now unless something is broken.
The
reason for that is that we're ramping up development for a new version of
OpenXRI
that conforms to the latest XRI Resolution draft.
Thanks.
Original comment by dre...@gmail.com
on 22 Jan 2008 at 8:12
Just to clarify: openid4java uses OpenXRI 1.0.1, which is distributed with
Xalan
2.6.0 and XMLSec 1.1.
I have asked William Tan of OpenXRI for his opinion about this issue:
http://groups.google.com/group/openid4java/browse_thread/thread/
d512cca297fbfbf9#80951bf4d1140493
Johnny
Original comment by Johnny.B...@gmail.com
on 22 Jan 2008 at 8:17
Is this at all related to running openid4java using Java 1.5's JAXP instead of
having
to rely on the distributed dom3 and xalan jars? Thanks
Original comment by martin.d...@gmail.com
on 13 Mar 2008 at 5:08
Any progress on this problem?
Original comment by cmeyer1...@gmail.com
on 24 Mar 2008 at 2:21
I haven't been able to obtain an update on the next openxri release.
Marcel Overdijk confirmed the workaround mentioned above: xalan 2.7.0 works
with
xmlsec 1.4.1.
Original comment by Johnny.B...@gmail.com
on 24 Apr 2008 at 8:20
The OpenXRI library has been upgraded to 1.2, and the new dependencies are
xalan
2.7.0 and xmlsec 1.3.0.
Also by the local XRI resolver (and its dependencies) is not included in the
default
package (the proxy resolver is used instead).
Original comment by Johnny.B...@gmail.com
on 7 May 2009 at 2:10
Original issue reported on code.google.com by
matts...@gmail.com
on 13 Jan 2008 at 10:17