Dan Kulp spotted a problem with the 1.5.4 release, which I'd like to
fix ASAP. Apparently this is causing a lot of problems for CXF and
ServiceMix, though there will likely be others.
The issue comes down to a dependency on OpenSAML libraries at init
time. As part of the work to make processors replaceable, I changed
the hard-coded class names (string constants) to XXX.class.getName().
This static code gets loaded at load time of the WSSConfig class,
which is central to the toolkit, and one of the class names is a
processor, which appears to have a static dependency on an openSAML
type. If the openSAML JAR can't be found, then toolkit initialization
fails.
Currently, the opensaml JARs are not deployed into central, which is a
problem for projects that can't find the JARs elsewhere (such as a
local mirror of central).
So one thing I'd like to do is fix the immediate problem, so that we
can avoid reliance on opensaml as a deployemnt requirement. We can
also work on deploying the opensaml JAR and POM to central, and I've
got an email out to Scott Cantor on that. But I'd prefer to make the
fix, as well.
There are a few other misc issues that could go into a 1.5.5 release.
Can anyone identify any others? And would we be open for a 1.5.5
release, hot on the heels of 1.5.4? I'd be willing to spin the
release (though I did loose a script I wrote as a result of a disk
failure, so I'd have to make up some lost ground).
Let me know what you all think. This opensaml issue could be a
problem for other mavenized projects that depend on WSS4J.
-Fred
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
