On Sat, 8 Jul 2000 13:12:41 -0400, Ken Klose <[EMAIL PROTECTED]>
wrote:
>>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.
The reason that it doesn't work is most likely that HTTPClient doesn't
use doPrivileged properly, or that this code wasn't assigned enough
permissions.
The former can be fixed by adding a layer that does doPrivileged before
delegating to HTTPClient, and the latter is a configuration error.
/Rickard
--
Rickard �berg
@home: +46 13 177937
Email: [EMAIL PROTECTED]
http://www.telkel.com
http://www.jboss.org
http://www.dreambean.com
===========================================================================
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".
