this can be caused by conflicting libraries. a simple check could be to check the userlib directory for possible duplicate jar files. Probably an older jar version of the same file is present, and is loaded before the new one. Remove the older version, clean your deployment directory and try again.
I already created a ticket for this ( 81051 ). I suggest you do also. This started with the latest SAML module. And this one could not be fixed by checking duplicate jar files (at least I could not seem to find any).
Regards,
Ronald
I've removed all the duplicate jars and it started succesfully.
thanks!
regards,
Niels