Hi Matthew,
Without some serious hacking in the Wicket internals this is not
possible. (I did it, but the code is too specific to share.) Wicket 1.5
will improve URL handling, then this case will hopefully be easily.
Regards,
Erik.
Matthew Welch wrote:
I have been happily using HybridUrlCodingStrategy for the common pages of my
current app, however I am now beginning to implement a section which has
slightly different requirements for the URL and while I have some idea about
where I can start to implement this custom URL handling, I would like the
advice of those more experienced that I to make sure I'm not heading down a
rathole.
My application will serve many different organizations. All users will see
the same set of pages, but the organization that they are choosing to view
(users can view the data from any organization) will affect the data on
those pages. I would like the urls to be something like this:
http://myapp.com/organization1/calendar
http://myapp.com/organization1/events
http://myapp.com/organization2/calendar
http://myapp.com/organization2/events
I would need to know the organization part of the URL before retrieving the
data for the page, so in reality it's nothing more that page parameter. In
all other respects, I would like to keep the functionality provided by
HybridUrlCodingStrategy, so would my best bet be to extend that strategy? Is
there somewhere else I should be inserting custom code to intercept the URL
before it gets to the coding strategy instead?
Matt
--
Erik van Oosten
http://day-to-day-stuff.blogspot.com/
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
