> I'm trying to work out a variation of what appears to be a problem
> previously encountered via JNDI/JMS and Tomcat. My specific
> configuration has a little bit of a different slant, though. I'm
> attempting to follow this route:
>
> JSP->JAAS->EJB->database
I figured out a work-around for JNDI/JMS. Actually, in my case it was just
for JNDI, though I was only using JNDI to use JMS! I have not used JAAS
before. Is it an extension? How is the extension loaded? You'll want to
make sure that the extension is loaded your code, and not by anything that
would be found in the standard CLASSPATH (as used by Tomcat), and it cannot
be done by including configuration information in a properties file or the
like.
For example, to use JCE, I had used the method of installing the provider by
putting an entry in the jre/lib/security/java.security file, and this had
the unfortunate side effect of causing those classes to be loaded by the
system class loaders rather than the JSP classloader that's going to look in
WEB-INF/lib for you. By loading the provider in my code instead
(Security.addProvider()) I was able to solve it. Hope this helps...
David
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, email: [EMAIL PROTECTED]
