From: Werner Donné (email@example.com)
Date: Tue Jan 14 2003 - 01:30:43 PST
Has the file $JAVA_HOME/jre/lib/security/java.security been modified by the
upgrade to Tomcat 4? If so, you could inspect the security.provider.<n> entries.
The first one would typically be Sun's provider (sun.security.provider.Sun). It
also contains an MD5 implementation.
David Tolpin wrote:
>>I have been using XEP with Tomcat without problem -- but after upgrading to Tomcat 4 I get the following error message:
>>cryptix.security.CryptoError: java.security.NoSuchAlgorithmException: class
>>configured for MessageDigest(provider: Cryptix)cannot be found.
>> at cryptix.security.MD5.getDigestImpl(MD5.java:87)
>> at cryptix.security.MD5.(MD5.java:82)
> This does not look like either a XEP bug or a java bug. Most probably something is missing
> in your classpath. However, if you send a test code that calls XEP from Tomcat off-list (firstname.lastname@example.org),
> I'll have someone look at it and resolve the problem.
> (*) To unsubscribe, send a message with words 'unsubscribe xep-support'
> in the body of the message to email@example.com from the address
> you are subscribed from.
> (*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
-- Werner Donné -- Re BVBA Engelbeekstraat 8 B-3300 Tienen tel: (+32) 486 425803 e-mail: firstname.lastname@example.org ------------------- (*) To unsubscribe, send a message with words 'unsubscribe xep-support' in the body of the message to email@example.com from the address you are subscribed from. (*) By using the Service, you expressly agree to these Terms of Service http://www.renderx.com/tos.html
This archive was generated by hypermail 2.1.5 : Tue Jan 14 2003 - 01:25:38 PST