-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Jess,
On 12/16/2010 11:56 AM, Jess Holle wrote:
> The JSP has not been deleted and a stack trace is logged like:
>
> org.apache.jasper.JasperException: Le fichier "/xxx/yyy/zzz.jsp" n'a pas
> été trouvé
> at
> org.apache.jasper.compiler.DefaultEr
On 12/16/2010 7:49 AM, Pid wrote:
On 16/12/2010 12:08, Jess Holle wrote:
Has anyone seen issues with JSPs that are present in an expanded web app
directory (i.e. deployed with an XML file pointing to a directory in WAR
layout rather than as a WAR) being found by Tomcat for a long time,
weeks eve
The JSP has not been deleted and a stack trace is logged like:
org.apache.jasper.JasperException: Le fichier "/xxx/yyy/zzz.jsp" n'a pas été
trouvé
at
org.apache.jasper.compiler.DefaultErrorHandler.jspError(DefaultErrorHandler.java:51)
at
org.apache.jasper.compiler.ErrorDispatch
On 16/12/2010 12:08, Jess Holle wrote:
> Has anyone seen issues with JSPs that are present in an expanded web app
> directory (i.e. deployed with an XML file pointing to a directory in WAR
> layout rather than as a WAR) being found by Tomcat for a long time,
> weeks even, and then suddenly no longe
2010/12/16 Jess Holle :
> Has anyone seen issues with JSPs that are present in an expanded web app
> directory (i.e. deployed with an XML file pointing to a directory in WAR
> layout rather than as a WAR) being found by Tomcat for a long time, weeks
> even, and then suddenly no longer being found t
Has anyone seen issues with JSPs that are present in an expanded web app
directory (i.e. deployed with an XML file pointing to a directory in WAR
layout rather than as a WAR) being found by Tomcat for a long time,
weeks even, and then suddenly no longer being found thereafter?
I've received se
