Actually, I've been thinking about this hybrid urls for a while (also
discussed it with igor) and I think it's something we should have. I'm
probably going to refactor current request encoding/decoding stuff so I
plan to address this there.
-Matej
Igor Vaynberg wrote:
the
Hello!
so what you want is instead of url doing this:
/mytree
click
/app?wicket:interface=
to do this
/mytree
click
/mytree?wicket:interface=
is this correct? and if so...
Yes, that's exactly correct!
i proposed this awhile back, and i think we decided not to proceed
David Leangen wrote:
Hello!
so what you want is instead of url doing this:
/mytree
click
/app?wicket:interface=
to do this
/mytree
click
/mytree?wicket:interface=
is this correct? and if so...
Yes, that's exactly correct!
i proposed this awhile back, and i think we
But this is something different. Bookmarkable urls doesn't mean that
there is no session. You have to store the state of tree somewhere.
What I mean is that the state of the tree is determined by the URL
parameter. I don't need to store the state anywhere else.
I'd like to do away with
In wicket 2.0 you can create pages that are not stored in session
(stateless pages).
Anyway, It's not possible with wicket to store state of tree in url, and
I doubt it ever will be. URL length is limited so it wouldn't work for
bigger trees. And wicket is managing state for whole pages, so it
Anyway, It's not possible with wicket to store state of tree in url, and
I doubt it ever will be. URL length is limited so it wouldn't work for
bigger trees. And wicket is managing state for whole pages, so it makes
no sense to ad-hoc store state of tree in URL either.
In my case, the
I see. With wicket 2.0 it should be possible to build a page like this.
With 1.2 it's not. I guess you can make your own tree subclassing
WicketTree and replace links on nodes with bookmarkable links, but that
won't really help you since the page will still be stored in session.
-Matej
David
Yeah, that should be doable. Only thing is that the tree has to use
bookmarkable links for the selection and fold/unfold items, and - if
you really want your tree to be independent from any prior session
state - you have to implement that tree such that it can construct
itself in the proper state
just for the record i was thinking along quiete different lines. i
wasnt thinking about the hybrid stuff we talked about i was thinking
about simply keeping the mount path prefix in the url once a mount is
hit cause it looks prettier and might help out with resource urls. i
wasnt thinking about
How would I go about getting the Tree component to listen to my mount
point? I mounted the page and would like to do away with the use of
sessions, but when I click on a node, I lose the mount point on the
page.
This is how the link is created:
protected Link createNodeLink(final
I did some digging, and this is about as far as I got for now:
When determining how to render the link for each node in the tree,
eventually WebRequestCodingStrategy.encode(RequestCycle, IRequestTarget)
is called.
Tracing a little further the following call is made:
the sharedresourcetarget is not the link url it is the node image's url. the link url will be represented by a ListenerInterfaceRequestTarget.so what you want is instead of url doing this:/mytreeclick
/app?wicket:interface=to do this/mytreeclick/mytree?wicket:interface=is this correct? and
12 matches
Mail list logo
