Hi David,
what you're doing with different brandings I do similar for different languages
with Wicket 1.3.
I want www.xy.de/de/ map to german and www.xy.de/en/ map to english interface of
the application.
What I did was extending WicketFilter to support path-extensions. I just
implemented:
public String getRelativePath( HttpServletRequest request )
{
String relPath = super.getRelativePath( request );
int idx;
int len = relPath.length();
if( len > 2 && (idx = relPath.indexOf( '/' )) >= 0 )
{
String lang = relPath.substring( 0, idx ).toLowerCase();
Locale locale = availableLocales.get( lang );
if( locale != null )
{
relPath = len > lang.length() ? relPath.substring( lang.length() + 1 )
: "";
request.setAttribute( LANG_ATTRIBUTE, locale );
}
}
return(relPath);
}
So, this takes the first part of the relativePath from the request and checks if
I have a supported language for it. If so, I set the Locale in the
request-Attributes and my Application can access that.
Something similar might work for you.
Best regards --- Jan.
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
