If your problem is that a webapp using hibernate loaded it's
configuration from webappclassloader and then stored the hibernate
loaded configuration in hibernate at common/ level, the problem is
probably that you have put hibernate in common classloader (so common
configuration, first webapp to
> From: Andrew R Feller [mailto:[EMAIL PROTECTED]
> Subject: Web app classloader loading JAAS LoginModule instead
> of server
>
> we found that the Hibernate login module was being initialized
> not by the server's classloader but the webapp's classloader!
> As w
While developing a custom JAAS module to use Hibernate for users'
authorization profiles on a new application, we found that the Hibernate
login module was being initialized not by the server's classloader but
the webapp's classloader! As we want to have different Realms declared
for each web appl
