Michael Jouravlev wrote:
Now I get it! /forminput is not a page name, it is the application
name, because each example is a separate application.
Now is it possible to have something like
/forminput/localetestform
instead of
/forminput?component=1
Most possibly this won't be possible with wicket in his current state.
Pages are normal objects, it's normal to have multiple instances of the
same class.
It is the same logical page, but it can be opened in different windows,
working with different models, etc.
Another question is several instances of the same page. You wrote that
"bookmarkable link creates a new page instance, thus the page gets new
id." Why would one need several instances of the same logical page? In
the same session? In the same window?
Let's say that you have master page and open 5 detail pages in different
windows/tabs. Each of the detail page is a different instance of the
DetailPageClass. If you were limited to one instance per class type, you
couldn't open multiple detail page at the same time.
-Matej
Considering that I do not want several instances of the same page, can
I have URL like above, with page name instead of component number?
Without using a filter :)
By the way, have you seen this project: http://tuckey.org/urlrewrite/
? But I would prefer not to use external tools to beautify my URLs, I
would have to create a whole map of nice URLs to component URLs, and
one of the features of Wicket is that I do not have to create mapping
files, right? ;)
Michael.
On 7/13/05, Matej Knopp <[EMAIL PROTECTED]> wrote:
I think this has to do with the way wicket pages are managed in memory.
Each page gets it's id, that's the number in component parameter.
The pages are stored in pagemap. The pagemap is a map with limited size.
Usually, there's 10 last pages stored in the pagemap. When new page is
created and stored in pagemap, it gets it's id assigned. The id incremental.
So first in your case there was page with id 0 displayed.
Later, new page was created and displayed, it's new assigned id was 1.
Bookmarkable link creates a new page instance, thus the page gets new
id. (Of course there are also other ways of creating page instances, not
just bookmarkable links)
/forminput does not identifies the page to render. Form input is
"application name". It's actually the URL wicket servlet is mapped to.
(/forminput/*)
you still have to know the id of page to render (the component attribute
in URL)
The wicket example consits of separate wicket applications. Each
application has one WicketServlet instance.
-Matej
-------------------------------------------------------
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-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
-------------------------------------------------------
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-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
