Hi Wicket-User, I have a similar situation - I'm tasked to build a site that appears to have multiple directories but that actually use the same set of pages. So for example:
http://mysite.com/clientname/Login http://mysite.com/clientname/Register http://mysite.com/clientname/OtherBookmarkablePath The first part of the path will be used to show a different look-and-feel - depending on the "clientname" you'll get different logos, text styles etc. (I can't make these different sites with alternative CSS or with variant pages, as they need to be created and customized on the fly through an admin section.) I'm not sure where to start looking, or what approach to take. Should that first path element be ultimately exposed on the Page as a PageParameter? Does this play havoc with getHomePage - how can I return a particular user's home page? Does the URL interpretation occur in the WebRequestCodingStrategy? (I'm stepping through a request at the moment, but haven't located where this particular magic happens yet!) (It would be great to just store the look and feel on the user's account, but I'm told that login and registration pages must also be branded.) Charlie. On Mon, Mar 3, 2008 at 1:10 PM, oliverw <[EMAIL PROTECTED]> wrote: > > I would like to allow the users of my site to choose which language the site > and the content is presented in by kind of prefixing the actual URL with a > virtual subfolder specifying the language. Example: > > Let's mount a page: > mount(new IndexedHybridUrlCodingStrategy("/foobar", FooPage.class)); > > And assume the following user access urls: > http://domain.com/foobar -> results in page foobar presented in english > http://domain.com/de/foobar -> results in page foobar presented in german > http://domain.com/fr/foobar -> results in page foobar presented in french > > What I would like to know if: > > a) It is possible to implement this without mounting /foobar multiple times > for all possible location (I think in order to get this to work I would have > to overrride WebRequestCodingStrategy.strategyForPath where simply all > mountpoints get iterated and checked for the target URL with > parth.startswith(key) > > b) Where to start? I debugged through most of the request cycle code but I'm > still not sure what's the best place to hook into. > > Any hint would be appreciated. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
