Otan wrote:
The problem with the extra dot-dot in the image src that arises when the
filter is map to /* seems to be fixed when I do this:
mountBookmarkablePage("/home", HomePage.class);
Now, the URL I see in the browser when I access the homepage is this:
http://server/context-path/home
instead
The problem with the extra dot-dot in the image src that arises when the
filter is map to /* seems to be fixed when I do this:
mountBookmarkablePage("/home", HomePage.class);
Now, the URL I see in the browser when I access the homepage is this:
http://server/context-path/home
instead of http://ser
And another thing, the problem occurs only on the homepage.
On 26/10/2007, Otan <[EMAIL PROTECTED]> wrote:
>
> When mapped with /*
> the URL of the homepage that I see in my browser is
> http://server/context_path/
>
> But a generated image path, which is wrong, looks like this:
> ../images/mainme
When mapped with /*
the URL of the homepage that I see in my browser is
http://server/context_path/
But a generated image path, which is wrong, looks like this:
../images/mainmenu-home.jpg which translates to
http://server/images/mainmenu-home.jpg
The correct path of the image src should be
image
This should work just fine.
What's the URL in your browser's address bar?
Wicket will automatically prepend things to make paths relative to the
context root.
Regards,
Al
Johan Compagner wrote:
filter should be mapped on /* thats why we have the filter.
I don't know why the ../ is generate
filter should be mapped on /* thats why we have the filter.
I don't know why the ../ is generated what is the url that you see in the
browser?
Maybe AlMaw can pitch in a bit.
johan
On 10/18/07, Otan <[EMAIL PROTECTED]> wrote:
>
> I'm using wicket beta 4 release.
>
> Images source path is wrong
I'm using wicket beta 4 release.
Images source path is wrong when my wicket filter is mapped to the url /*
The reason is because the src path of each images changes into something
with double dot (..)
Example:
my wicket filter:
Wicket
org.apache.wicket.protocol.http
