On 7/13/05, Gili <[EMAIL PROTECTED]> wrote:
> Alternatively, maybe I'm just wrong on all of this and we should jump
> straight to pretty names. Take class Page and add getURLName() and this
> method returns the pretty name for this component within the URL.
>
> Then say you have:
>
> http://hostname.com/Main/bookmarkablePage=a.b.c.d
>
> it would become:
>
> http://hostname.com/Main/myPrettyName
>
> and if myPrettyName contained a panel called "myPanel" its path would
> be:
>
> http://hostname.com/Main/myPrettyName/myPanel
Excuse me for breaking into the dev thread, I just want to remind
about a catch, that I stumbled upon couple of days ago (with Struts,
but should not make a difference, I guess)
Wicket is doing redirect to render, not a forward. So, the address in
the address bar is *the real address* which server is using. So, if
you have relative references to pictures, CSS or other stuff, it won't
work after you step from
http://hostname.com/Main/myPrettyName
to, say
http://hostname.com/Main/myPrettyName/myPanel
Because now the resource is one level up, and you cannot add ..\ dynamically.
This is a catch with "real pretty names" with slashes, that a name is
treated as path. So, you might want to establish a "root" application
name/context somewhere in the accessible place, and always use it when
you build path to resources.
So, if someone includes CSS stylesheet directly to HTML template or
header or whatever, it would break after he changes one level up/down
:-((
Michael.
-------------------------------------------------------
This SF.Net email is sponsored by the 'Do More With Dual!' webinar happening
July 14 at 8am PDT/11am EDT. We invite you to explore the latest in dual
core and dual graphics technology at this free one hour event hosted by HP,
AMD, and NVIDIA. To register visit http://www.hp.com/go/dualwebinar
_______________________________________________
Wicket-develop mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-develop
