Ah hah. :-) Well spotted. We probably have an old version of xalan on our
classpath as in the dark past we used cocoon to implement our webpages - yuck.
If I have...
Main-Class: org.apache.xalan.xslt.Process
Created-By: 1.2.2 (Sun Microsystems Inc.)
Class-Path: jaxp.jar xerces.jar crimson.jar
at the top of the xalan.jar MANIFEST.MF file does that mean I am using 1.2.2
:-)
Dan Diephouse wrote:
It seems you're using the wrong version of xalan. If you have the
xml-security 1.2 jar, you need to use Xalan 2.6. If you want to use
Xalan 2.7, you need to use xml-security 1.3:
http://www.apache.org/dist/java-repository/xml-security/jars/xmlsec-1.3.0.jar
Xml sec 1.3 will be bundled in the final release along with Xalan 2.7
Hope that helps,
- Dan
Stuart Barlow wrote:
Continuing with UserTokens...
At the following line in my code...
client.addOutHandler(new WSS4JOutHandler(properties));
I get the stack trace...
[EMAIL PROTECTED]@[EMAIL PROTECTED]@[EMAIL PROTECTED]@39ab89-
Unable to patch xalan function table.
java.lang.NoSuchFieldException: m_functions
at java.lang.Class.getField(Class.java:919)
at org.apache.xml.security.Init.registerHereFunction(Unknown Source)
at org.apache.xml.security.Init.init(Unknown Source)
at org.apache.ws.security.WSSConfig.<init>(WSSConfig.java:72)
at org.apache.ws.security.WSSConfig.getNewInstance(WSSConfig.java:95)
at org.apache.ws.security.WSSConfig.<clinit>(WSSConfig.java:47)
at
org.apache.ws.security.WSSecurityEngine.<clinit>(WSSecurityEngine.java:51)
at
org.apache.ws.security.handler.WSHandler.<clinit>(WSHandler.java:61)
at
com.peopledoc.rhum.webservices.LogonWSSecurityTest.testLogonAndLogoff(LogonWSSecurityTest.java:25)
Is this because I am on Java 1.4 ?
thanks,
Stuart
--
Stuart
