> As a side note: Wicket doesn't read the context path from web.xml, but
> gets it from the servlet API/ container. I'd expect this behaviour to
> be the same whether you are running a standalone servlet container or
> one embedded in OSGi...

That's weird, because my call to getApplicationSettings().getContextPath
() always returns "/" (which is incorrect) unless I explicitly set it to
the correct value. When I do set it, it returns the correct value.

That said, my PageLinks are correctly rendered when I DON'T set the
context path, and the context path is doubly rendered when I do set it
explicitly.


Anyway, if nobody else is getting this, it must be my setup, so I'll
deal with it. My work around is to not explicitly set the context path
(so my Page links are rendered correctly) and I'll override
PrependContextPathHandler to fetch my non-Page resources from a public
URL.


Thanks again for all your patience.





-------------------------------------------------------
This SF.Net email is sponsored by xPML, a groundbreaking scripting language
that extends applications into web and mobile media. Attend the live webcast
and join the prime developer group breaking into this new coding territory!
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=110944&bid=241720&dat=121642
_______________________________________________
Wicket-user mailing list
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user

Reply via email to