Guys, the problem is another, lets recap:
I've a folder with a javascript, a css and some images. From both the css
and the javascript I references these images using a relative path. For
example in the css url(the-image-1.gif) and in the javascript file image.src= '
the-image-2.gif'.
The css works fine instead the javascript image link is broke.
The problem is that a relative path in a CSS is relative to the location of
the css itself, so loading the css under the wicket
/resource/package.name.Class/ path it works fine.
BUT relative path in a javascript are relative to the page which loaded the
script NOT the script location, so the relative link will break!
Thanks, Paolo
On 4/16/07, Eelco Hillenius <[EMAIL PROTECTED]> wrote:
On 4/16/07, Igor Vaynberg <[EMAIL PROTECTED]> wrote:
> in wicket 1.2.3 we do not allow default access to packaged resources
without
> explicitly adding a shared resource do we? i think that is the problem.
his
> css is a shared resource, but everything alongside it is not. so this
would
> for in 1.3 but not in 1.2.3.
Duh! Indeed. I completely forgot about that.
Eelco
-------------------------------------------------------------------------
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
Wicket-user@lists.sourceforge.net
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
Wicket-user@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/wicket-user
