maybe it is because wicket now always adds a / to the end of the servlet
mapping. this was inconsistent in the past, sometimes urls were
/context/mapping?wicket:id... and sometimes they were
/context/mapping/?wicket:id=...
the problem was that /context/mapping?wicket:id urls did not always get
mapped to the servlet properly, but the /context/mapping/? did, so that is
the option we went with.
is that the problem? the browser thinks you are in /context/mapping while
your link assumes you are in /context ?
what is your servlet mapping?
-igor
On 4/26/07, dzenanr <[EMAIL PROTECTED]> wrote:
Not a single line of code has been changed between the two versions. The
version with Wicket 1.2.5 jars displays property web pages using css files
in the css subdirectory of the web application root directory, and the
version with Wicket 1.2.6 jars cannot find the css files that are in the
same directory as in the previous version.
--
View this message in context:
http://www.nabble.com/from-1.2.5-to-1.2.6-tf3647980.html#a10202910
Sent from the Wicket - User mailing list archive at Nabble.com.
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
