I have observed a behavior that I could swear was not there
a month ago, and I'm wondering whether it is due to any recent
changes in Turbine. Here are the symptoms.
I bring up Resin, and hit /app/servlet/app; the URL is rewritten
as /app/servlet/app/redirected/true, and I can work with the app.
Then, I bring Resin down, recompile the app, update JARs (my app,
as Turbine, is one JAR that I put into WEB-INF/lib) and bring
Resin back up. Then, on the browser, I delete "/redirected/true"
from the URL, and hit enter.
I could swear that a month ago those steps would refresh the
whole app; all my Turbine services were reloaded, and the app
restarted fine. Today, the services are NOT reloaded, and I have
to hit Refresh to force them to be initialized (at which point,
both "early inits" and "init" are executed).
Not sure if this is related, but I have also seen pages that show
DB data that seem to be cached: hit the "show page", show n records,
go to the "add page", add one record, select again the "show page"
(NOT by hitting the Back button, but by going there again) and only
n records are shown; hit Refresh, and n+1 records are shown.
People in my team report the same effects with Tomcat and other
browsers (IE and Netscape over linux). Anybody can think of a reason
for these symptoms to be happening? The part about services not
being reinited is what bothers me the most...
Thanks,
--
Gonzalo A. Diethelm
[EMAIL PROTECTED]
------------------------------------------------------------
To subscribe: [EMAIL PROTECTED]
To unsubscribe: [EMAIL PROTECTED]
Search: <http://www.mail-archive.com/turbine%40list.working-dogs.com/>
Problems?: [EMAIL PROTECTED]
