the context path for the site is /myweb but wicket servlet path was /*

i have changed the wicket servlet path to /app and its working faster now so
that the full path is www.mysite.com/myweb/app

it really does not have anything to do with the code but web.xml config

however,

in my html, i have <img src="images/myimage.gif" />
and whenever i have a wicket image like <img wicket:id="image"
src="/myweb/images/myimage.gif" />

notice that i had to append the context path for the webapp (not wicket
servlet path). until I did that my wicket images dont load in
wicket1.2.6unlike wicket
1.2.4



On 7/23/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
>
> On 7/20/07, Ayodeji Aladejebi <[EMAIL PROTECTED]> wrote:
> > I recently upgraded to wicket 1.2.6 and although this time my
> application
> > path is /*
>
> With a servlet? Sure that's a good idea?
>
> > and i realized for each page refresh or event, the same sets of images
> seems
> > to be loading all over again making loading appear slow
>
> How do you add these images? Any code you can share?
>
> Eelco
>
> -------------------------------------------------------------------------
> This SF.net email is sponsored by: Splunk Inc.
> Still grepping through log files to find problems?  Stop.
> Now Search log events and configuration files using AJAX and a browser.
> Download your FREE copy of Splunk now >>  http://get.splunk.com/
> _______________________________________________
> Wicket-user mailing list
> Wicket-user@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/wicket-user
>
-------------------------------------------------------------------------
This SF.net email is sponsored by: Splunk Inc.
Still grepping through log files to find problems?  Stop.
Now Search log events and configuration files using AJAX and a browser.
Download your FREE copy of Splunk now >>  http://get.splunk.com/
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to