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
David Leangen-8 wrote:
What version are you using?
I'm using 1.4.
It wouldn't have occurred to me that it would be so difficult. I know it may
seem odd, but URL control is actually very important here because
organization identity is vital in the domain that the app will serve.
Hmmm
In the past, I've accomplished something similar in a hack-ish sort of way
that may work for you. Basically, I extended the WicketFilter and stripped
the first argument off, storing it in the request before Wicket used the URL
to determine the requested page. Maybe you can go down a similar
Jeremy Thomerson-5 wrote:
In the past, I've accomplished something similar in a hack-ish sort of way
that may work for you. Basically, I extended the WicketFilter and
stripped
the first argument off, storing it in the request before Wicket used the
URL
to determine the requested page.
Oh, yeah - okay, so there was a little difference. It depends on your setup
- mainly - will you ever need links from two organizations on the same page?
Basically, what I was doing was creating branded sites. So, here's the gist
of what I had:
Apache frontend, based on site, would proxy to
What version are you using?
I'm using 1.4.
Ok, then I can't really help you much.
URL control is actually very important here because
organization identity is vital in the domain that the app will serve.
Agreed. IIUC, it may be easier in 1.4:
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,
