> > > That why it is dangerous to have the mount(string,coder)
> method and
> > > why it is removed in wicket 2.0 (and it will stay that way)
> >
> > ok, basically this comes to: you never got it working/ dont
> understand
> > it so stripped it...
>
>
> what a stupid thing to say consideri
> That why it is dangerous to have the mount(string,coder)
> method and why it is removed in wicket 2.0 (and it will stay that way)
ok, basically this comes to: you never got it working/ dont understand it so
stripped it... ok if this is your way - im not discussing this item any
longer, ill use
yeah, but you forgot to put the appropriate first (and following) page param
to it:
"/path/to/page2" -> these are the prePageParams for me here, that i grab
each time i use a new one...
so you manually change your link to be at the mountpoint...
URLs are build like that: preParams / postParams
> It just has to be in sync. So thats why i removed that param
> in the mount.
thats the point !
currently you can take it out of sync in wicket 1.2.x if you want - while in
2.0 you're forbidden to do so -> loss of functionality
the thing that i do is to hold a (pre)PageParam in my session an
it did. you just didnt understand it yet -
in wicket 1.x you can mount a page to
/de
/en
and not having the IndexedPar...egy putting the /de everytime in front - but
you were responsible for that by having the 0 param beeing set to e.g: de .
A nice URL paradigm begins by creating it on paper an
