ve attached
> the most recent tomcat.policy file.
>
> > -Original Message-
> > From: Antony Bowesman [mailto:[EMAIL PROTECTED]]
> > Sent: Monday, May 21, 2001 12:49 AM
> > To: [EMAIL PROTECTED]
> > Subject: Re: JSP and SecurityManager [was RE: 3.2.2. When
SecurityManager [was RE: 3.2.2. When's it
> shipping?]
>
>
> Marc Saegesser wrote:
> >
> > The null check is simple enough and its already been tested in 3.3
> > so I feel comfortable making the change without a beta. I'll commit
> > the change to
Marc Saegesser wrote:
>
> The null check is simple enough and its already been tested in 3.3
> so I feel comfortable making the change without a beta. I'll commit
> the change today.
Great, thanks!
> Another question regarding using the security manager and JSP. If
> I use the default tomcat.
n
> Sent: Friday, May 18, 2001 11:09 AM
> To: [EMAIL PROTECTED]
> Subject: Re: JSP and SecurityManager [was RE: 3.2.2. When's it
> shipping?]
>
>
> Hmm, I had thought those were getting added automatically, like the
> read FilePermission for the context root. Sure, you
Hmm, I had thought those were getting added automatically, like the
read FilePermission for the context root. Sure, you can add those
to the default grant policy entry in tomcat.policy.
Glenn
Marc Saegesser wrote:
>
> The null check is simple enough and its already been tested in 3.3 so I feel
The null check is simple enough and its already been tested in 3.3 so I feel
comfortable making the change without a beta. I'll commit the change today.
Another question regarding using the security manager and JSP. If I use the
default tomcat.policy file I can't access any JSP pages because I