Forum Discussion
omatzura
17 years agoSuper Contributor
Hi,
the reason it has changed is probably because the ws-security library has been updated and the new version sends this version instead.. hm... I'll dig into this, to work around the issue you could try replacing the wss4j-1.5.4 library in 2.5 with the 1.5.3 version in 2.0.2 (let me know if that helps!)
regards,
/Ole
eviware.com
the reason it has changed is probably because the ws-security library has been updated and the new version sends this version instead.. hm... I'll dig into this, to work around the issue you could try replacing the wss4j-1.5.4 library in 2.5 with the 1.5.3 version in 2.0.2 (let me know if that helps!)
regards,
/Ole
eviware.com