Thanks a million!
I did not change any of those settings, _but_ 1.0.4 introduced an
incompatibility.
Checking for changes in the skin file is now off by default:
https://issues.apache.org/jira/browse/TRINIDAD-761
It started to work again after explicitly setting CHECK_FILE_MODIFICATION to
true.
There should have been a prominent link to release notes, that list changes to
be
made when upgrading Trinidad.
In fact the "Release Notes" section on the trinidad main page still refer to
1.0.3
and do not even include changes from 1.0.2 to 1.0.3.
Martin Hinterndorfer wrote:
Hi Stephen!
Have you changed some of the configuration parameters described in:
http://myfaces.apache.org/trinidad/devguide/configuration.html
ie:
org.apache.myfaces.trinidad.USE_APPLICATION_VIEW_CACHE
changes the behaviour of pages beeing cached.
or:
org.apache.myfaces.trinidad.CHECK_FILE_MODIFICATION
could have influenced your described behaviour.
hope, it helped!
Martin
2008/2/16, Stephen Friedrich <[EMAIL PROTECTED]
<mailto:[EMAIL PROTECTED]>>:
I am in the finishing stages for my web app. There's still a lot of
styling to do
which involves tweaking the skin file and checking on all required
browsers.
That job was barely acceptable while I could simply repackage the
skin file and
reload the page to see the effect.
However recently that just stopped working. I have to redeploy the whole
application for Trinidad to pick up the changes.
I'm going nuts!
(Some days ago I had to update from 1.0.3 to 1.0.6, but I think at
first it still
worked.)
Can anybody help?
