we are new to wicket,
and currently trying to optimize and performance tune our wicket
application.
using 1.5.3. 

we tried to get the caching configuration up and running. red this: 
https://cwiki.apache.org/WICKET/migration-to-wicket-15.html#MigrationtoWicket1.5-inIResourceSettingsmethodsetAddLastModifiedTimeToResourceReferenceUrl%2528%2529hasbeenreplacedbyIResourceCachingStrategy
migration to 1.5.  already, 

and we have set: /getResourceSettings().setCachingStrategy(strat); /during
application init.

we have CSS and JS in the Base-Frame.html header as link and script. and we
have a lot of images we currently implement something like this:

                Image img = new Image("logoutImg") {
                        protected void onComponentTag(ComponentTag tag) {
                                super.onComponentTag(tag);
                                tag.put("src", baseUrl + "/images/logout.png");
                        }
                };

now we always geht 
*Pragma No-cache
Cache-Control   no-cache
*
for all resources and pages.

now we have experimneted with using an extra servlet filter, which
overwrites those headers ...

could anyone provide a running working example, or some tips for getting
this up and running ? 

thanks.







--
View this message in context: 
http://apache-wicket.1842946.n4.nabble.com/Caching-Imagages-CSS-JS-in-Wicket-1-5-3-tp4121068p4121068.html
Sent from the Users forum mailing list archive at Nabble.com.

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to