> I think I know your use-case, but perhaps you could elaborate for the > rest of the audience.
Sure, though I'm not sure how relevant others will find this to their own use of pax-wicket... Essentially, after a good talk with Niclas the other day, I was able to confirm that the intent of pax-wicket is to have one instance of a wicket application that acts as a host to any number of page clusters. [As a side note, I call "page cluster" any group of one or more pages that act together as what is often called an "application". However, the word "application" is so overloaded...] Anyway, for my use case, I need each page cluster to be "mounted" on a given partition in the URL space. The problem with the default url coding scheme with Wicket is that for all stateful pages, you lose any "pretty url" configuration that you associate with BookmarkablePages. So, even if a given page is mounted in url space, as soon as that page becomes stateful, you lose your pretty url configuration. For example, if I mount a page RegistrationPage in wicket on /home/registration, and if I put some kind of component on that page (say a form in our case), any use of that component (like submitting the form) will take us to some page like: /home/?wicket:interface=:0:::: rather than /home/registration/?wicket:interface=:0:::: Note that the former is mounted on the root path (relative to wicket's context path), and no longer on the mount point for the page as we intended. The only way to get this working as I intend it to is to provide my own custom IRequestCycleProcessor. In any case, there may be other use cases where you need to provide your own IRequestCycleProcessor, so having the ability to do so is probably not a bad thing. Cheers, David _______________________________________________ general mailing list [email protected] http://lists.ops4j.org/mailman/listinfo/general
