You can use the header approach just fine on 1.2.x.
If you were using 1.3.x then your pointing two paths at the same wicket
app would work fine too, I think.
If you're running behing mod_proxy I'd strongly recommend upgrading to
1.3.0-beta2 - it solves a bunch of issues with this by using relative
URLs everywhere instead.
Regards,
Al
David Leangen wrote:
I'd suggest a better way of doing this...
...
For the different inbound URLs, get Apache to add a header
"X-Branding" with some appropriate String.
...
Oh, that's interesting, too...
I assume you're using 1.3.x for this?
No... unfortunately, I'm stuck on 1.2.6 for now. Why? Won't this work on
1.2.6?
Cheers,
Dave
-----Original Message-----
From: Al Maw [mailto:[EMAIL PROTECTED]
Sent: 16 August 2007 21:07
To: [email protected]
Subject: Re: Caching the context path
David Leangen wrote:
so what exactly are you doing?
Well... the end goal is to use the URL as the controlling input for the
branding of my application. So I have a BrandingService with
something like:
I'd suggest a better way of doing this...
Run a single Wicket app.
For the different inbound URLs, get Apache to add a header "X-Branding"
with some appropriate String.
Add a HeaderContributor in your base page which points to the
appropriate CSS for that attribute, dug out of the WebRequest object.
I assume you're using 1.3.x for this?
Regards,
--
Alastair Maw
Wicket-biased blog at http://herebebeasties.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
!DSPAM:46c442b3323394576627205!
--
Alastair Maw
Wicket-biased blog at http://herebebeasties.com
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
