Matt,
I have done something similar, but depending on the version of Wicket
you use, I wouldn't necessary recommend it. Things can get a little
messy.
I did this in 1.3.x. IIRC, I was told this was made easier in 1.4.
What version are you using?
=dml
On Apr 20, 2009, at 1:54 PM, 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
---------------------------------------------------------------------
To unsubscribe, e-mail: users-unsubscr...@wicket.apache.org
For additional commands, e-mail: users-h...@wicket.apache.org
