> > Because of the JSP reloading bug found in Jasper 2, I plan to abandon
the
> > 4.1.1 milestone, and release a 4.1.2 milestone soon to replace it.
> >
> > Comments ?
> >
>
> I'm not completely up to date on Jasper2 (I may back-port the finallies to
> 3.3.x at some point, but at the moment that's the only change I care
about),
> but my understanding is that the "bug" is nothing more than the default
> value of an attribute not being backwards compatible.

That's what I thought at first, but it turned out it didn't work at all,
even when "development" was set to true. The only way to reload a JSP was to
either:
- do a reload of the webapp through the manager
- be patient (up to 5 minutes, which was the delay of the background thread
checking)

So for normal users, 4.1.1 won't reload JSPs :-(

> Now, the 4.1.x
> release scheme allows you to release 4.1.2 just to change this, but since
> 4.1.x is still "early access", you can achieve the same affect by
> broadcasting the attribute on the tomcat-dev and tomcat-user lists. As
such,
> I can't get more enthusiastic than +0.

Remy


--
To unsubscribe, e-mail:   <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>

Reply via email to