Why not try to continue if getRealPath() returns null? The Servlet 2.2 spec
allows containers to return null if they feel like it. (Haven't checked
this in 2.3).
That is, how about something more forgiving like this instead:
try {
// see if file exists on the filesystem firs
> Synopsis:
> TagAttributeInfo constructor signature is incorrect
>
> Description:
> The constructor's signature is inconsistent with the javadoc.
> The implementation's signature is
>
> TagAttributeInfo(String, boolean, String, boolean)
>
> The javadoc specifies it as
>
> TagAttributeInfo
Pierre Delisle is wondering:
> -
> Bug #55
>
>-
>Synopsis:
> Default for included files is 8859_1, with no option to
> set otherwise.
> [SNIP]
> I'm not sure I fully understand what's described there,
> so here is what I believe should be done.
>
> The "encoding" for a
[EMAIL PROTECTED] wrote regarding JspFactory problems:
> We're using Jasper (for a number of reasons) inside Weblogic, and have
seen
> similar problems [JspFactory.getDefaultFactory() fails, or
> factory.getPageContext() fails] intermittently -- usually at startup or
> during heavy load testing.
It's a long story, but I'm working on a project where Jasper 3.x is embedded
inside a servlet, which can then be deployed to the container of our
customer's choice. The servlet uses JSP files as templates, which is where
Jasper comes in.
In this type of environment, sometimes thing can go really
