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 Tomcat with an additional path element ahead of the proxy like this: Your request URL: www.site-one.com/foo Apache proxied to Tomcat: www.site-one.com/org-one/foo My filter modified that so that it was again /foo and stuck the org into the session So, the Wicket-generated links of /foo or /bar worked fine - because the org didn't actually appear in the URL *path* - it was based on URL *domain* Does that make sense? I guess it would only work if you could use domain or subdomain based orgs rather than URL path based. -- Jeremy Thomerson http://www.wickettraining.com On Mon, Apr 20, 2009 at 4:32 PM, Matt Welch <[email protected]> wrote: > > > 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. Maybe you can go down a similar route? > > > Thanks. That's something to consider. How did you get wicket to write out > the correct URL's for links though? > > -- > View this message in context: > http://www.nabble.com/Custom-URL-Handling-tp23130367p23145343.html > Sent from the Wicket - User mailing list archive at Nabble.com. > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [email protected] > For additional commands, e-mail: [email protected] > >
