> From: Stephen More [mailto:[EMAIL PROTECTED]
> Subject: Re: JAASRealm problem moving from 5.5.23 -> 5.5.26
>
> 5.5.26 seems to work fine when useContextClassloader=true
> 5.5.23 no longer works if useContextClassloader=true
(I assume useContextClassloader is really useContext
>>
>
> Take out the path attribute; it's not allowed unless the element is
> in server.xml (where it should never be, these days). It should be ignored,
> but...
Done.
>> ...
>> useContextClassLoader="false" />
>
> Just for grins, what happens if you set useContextClassloader to
> From: Stephen More [mailto:[EMAIL PROTECTED]
> Subject: Re: JAASRealm problem moving from 5.5.23 -> 5.5.26
>
>
Take out the path attribute; it's not allowed unless the element is
in server.xml (where it should never be, these days). It sho
On Wed, Jun 18, 2008 at 2:10 PM, Caldarale, Charles R
> Just to verify, your declaration is within the webapp's ,
> correct?
> Could you post the element for the webapp? I'd like to see if
> there's anything odd in it.
My declaration is stored in META-INF/context.xml of the war.
> From: Stephen More [mailto:[EMAIL PROTECTED]
> Subject: Re: JAASRealm problem moving from 5.5.23 -> 5.5.26
>
> The binary download does not output a stack trace for the error. I
> added the stack trace to the src and recompiled. Here it is:
Thanks. This will take a little
>> This setup has worked out of the box on both 5.5.23 and 6.0.16 without
>> any changes to my CLASSPATH environment variable.
>
> Do you have anything in CLASSPATH? You shouldn't.
Nope. CLASSPATH is empty.
>> If I need to run multiple versions of a realm am I now forced
>> to run multiple insta
> From: Stephen More [mailto:[EMAIL PROTECTED]
> Subject: Re: JAASRealm problem moving from 5.5.23 -> 5.5.26
>
> Is "Tomcat's classpath" defined somewhere in the docs ?
It's normally just bin/bootstrap.jar; probably not explicitly defined in the
docs, just di
>> Just after that I am seeing a SEVERE message that it can not find my
>> classes where I extend javax.security.Principal. These classes can be
>> found in the deployed war file.
>
> Which is not where they're supposed to be. To quote from the doc: "Place
> the compiled classes on
> Tomcat's cl
> From: Stephen More [mailto:[EMAIL PROTECTED]
> Subject: JAASRealm problem moving from 5.5.23 -> 5.5.26
>
> Just after that I am seeing a SEVERE message that it can not find my
> classes where I extend javax.security.Principal. These classes can be
> found in the deployed wa
I have been using 5.5.23 with a JAASRealm for some time now.
In trying to upgrade to 5.5.26 I am now seeing a new log entry in catalina.out
Jun 18, 2008 8:40:09 AM org.apache.catalina.realm.JAASRealm parseClassNames
Just after that I am seeing a SEVERE message that it can not find my
classes whe
10 matches
Mail list logo
