im not sure on this one. If every component may be hooked to a unique URL
Part, then it wont matter at what location it is, would it?
I mean i use the bookmarkable system we have and just transfer it to the
components.
e.g: Component A = mounted to(/A)
Component B = mounted to (/B)
Component C = mounted to (/C)
if a page now is called using /page/a/12/b/13
This is going towards a string based approach like e.g. model 2
frameworks work. Wicket is based around Java objects, not strings, for
it's state and it is uses components, rather than actions.
Furthermore, components live in a tree, with one root component, Page.
The fact that components live in such a hierarchy makes that they can
cooperate with each other in an easy fashion, traverse their children,
etc. This is very fundamental for Wicket, and thus mounting separate
components cannot be supported.
Eelco
