-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Robert,
On 12/8/11 9:19 AM, Robert Winch wrote:
> That is good information to know. We plan on updating to 7.0.23
> within the next few weeks.
Be aware that there is a bug in 7.0.23 that causes a hang-on-startup
if a webapp does not have a defined.
On Thu, Dec 8, 2011 at 9:02 AM, Mark Thomas wrote:
> On 08/12/2011 14:19, Robert Winch wrote:
> > On Thu, Dec 8, 2011 at 4:29 AM, Pid wrote:
> >> You say below that the compiled tags & JSP don't appear to have been
> >> recompiled - either upgrade, or clear the work directory to ensure that
> >>
On 08/12/2011 14:19, Robert Winch wrote:
> On Thu, Dec 8, 2011 at 4:29 AM, Pid wrote:
>> You say below that the compiled tags & JSP don't appear to have been
>> recompiled - either upgrade, or clear the work directory to ensure that
>> they have been.
>>
>
> I'm not sure I understand. Is there a
On Thu, Dec 8, 2011 at 4:29 AM, Pid wrote:
> On 07/12/2011 17:32, Robert Winch wrote:
>
> > 3) I have looked for any jars included in the war that might contain the
> > wrong JspTag or PageContext. I tried to do an open type in Eclipse on
> both
> > classes and found jsp-api and servlet-api both
On 07/12/2011 17:32, Robert Winch wrote:
> We have a web application that was consistently getting a VerifyError
> whenever a jsp invoked a custom tagx. The jsp is a SiteMesh decorator that
> uses a custom tagx to display a Spring Security Authentication object. The
> issue was resolved by restarti
We have a web application that was consistently getting a VerifyError
whenever a jsp invoked a custom tagx. The jsp is a SiteMesh decorator that
uses a custom tagx to display a Spring Security Authentication object. The
issue was resolved by restarting the war using the Tomcat Manager, but I am
con
