>Exactly. Which is trivial if you simply:
>1) Don't package the implementation with your EJB (i.e. don't put it in
>the EJB-jar)
>2) Add it to the system classpath or similar
>
>Let the classloader delegation model do the rest.
I have had this same problem with using a library (specificially HTTPClient)
that uses threads. And this does not solve it. From the very beginning the
only classes in my EJB-jar files were the Home, Remote and Bean
implementation classes. The HTTPClient library was always referenced
through the classpath (the J2EE_CLASSPATH environmental variable which gets
appended to several other paths as the CPATH environmental variable and then
passed to the JVM on the command line using the -classpath option).
Furthermore I was getting the same security exception when trying to call
this library from a servlet running inside of J2EERI.
I finally gave up on HTTPClient and started using URL and URLConnection,
which will work fine until I need to do an HTTP POST.
===========================================================================
To unsubscribe, send email to [EMAIL PROTECTED] and include in the body
of the message "signoff EJB-INTEREST". For general help, send email to
[EMAIL PROTECTED] and include in the body of the message "help".
