In SignIn example link look like this: <a href="signin">signin</a> As
you can see, there is no additional parameters, it simply navigates to
signIn. WebRequestCycle considers this link as a homepage, and calls
setResponsePage(homePage). At least in this case Wicket does not
create a new instance. But in case of bookmarkable page Wicket calls
Page newPage =
session.getPageFactory().newPage(pageClass,
new PageParameters(getRequest().getParameterMap()));
which is not exactly what I want. But I have not gotten there yet, so
I cannot tell for sure ;-)
Going to a home page That is what that href does that only goes to a
home page
Then a new page is created yes. But that is the thing that get's hit
from outside youre webapplication
I only talk about things when youre are inside youre web application.
Those links in Page X or Page Y are controlled by you.
Bookmarkable pages or HomePages are just entry points to start a wicket
session, start a page
and go forward from that point on. (and then you are in control of the
complete flow)
You could create youre own PageFactory, but i guess you want to have a
Session Pagefactory.
Not an application page factory. Don't think that is possible right now.
What application object are you talking about?
The wicket? That one is not stored in the session!
Application is global, only one instance lives there.
If you want to share things you have to store it really in the session.
how about getSession().getApplication() ? Oh, I see, getSession() is
not HttpSession. I think Session object should be renamed to
WicketSession to avoid ambiguity.
Session.getApplication() should be removed.
you should do now: Application.get()
I do agree here that session.getApplication() looks like that you get a
session thing. But it isn't.
Link class in just an abstraction. It all boils down to a good old
HTTP/HTML. Wicket parses a regular HTTP requests, which does not know
about Link objects. I already gave you example of start page in SignIn
example, the page is pure HTML.
Before creating my own Link objects, I need to understand how Wicket
parses request parameters.
But you are right that in the end of the day I will have to create a
Link, which will generate proper <a href> for me.
Ok but if you want to give parameters from outside youre webapplication
directly to a page inside
youre webapplication then you can use bookmarkable urls:
<a href="signin/bookmarkablePage=xxxxx?param=value">signin</a>
then a page will be created (like it should you jump inside an
application maybe for the first time)
and the page will get that PageParameters in its constructor (if it has
such a constructor)
johan
-------------------------------------------------------
SF.Net email is Sponsored by the Better Software Conference & EXPO
September 19-22, 2005 * San Francisco, CA * Development Lifecycle Practices
Agile & Plan-Driven Development * Managing Projects & Teams * Testing & QA
Security * Process Improvement & Measurement * http://www.sqe.com/bsce5sf
_______________________________________________
Wicket-user mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/wicket-user
