From: David Tolpin (email@example.com)
Date: Thu Jun 19 2003 - 09:34:24 PDT
> but I suspect this behaviour may be caused by the ClassLoader XEP uses to
> load the cryptix and xt JAR's. Is there anything peculiar about the way XEP
> accesses classes within the Cryptix and/or xt JAR's? Incidentally, this
> behaviour is not occuring when we test within Websphere Application
> Developer, only when we deploy it to our Websphere installation on Solaris,
> again leading me to believe this a ClassLoader issue.
I am aware of people on the list who have more experience than me in deploying
XEP in J2EE envrinoment. I hope they'll help you with deployment.
Internally, XEP uses default class loader and the only 'peculiar' thing
it does is the following code in com/renderx/util/License initialization
if(provider==null) java.security.Security.addProvider(new cryptix.provider.Cryptix());
(*) To unsubscribe, send a message with words 'unsubscribe xep-support'
in the body of the message to firstname.lastname@example.org 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 : Thu Jun 19 2003 - 09:36:09 PDT