I am in the process of porting an existing struts/tiles to wicket. While I have used Struts, I have not used Tiles. From what I gather, Wicket can do the same functionality as Tiles via Border components. I will assume that this is the way to go. If not please, advise what is the best approach.
In a nutshell, the app uses a URL attribute to signify who the caller is and subsequently what template should be used. I believe this is standard protocol as I have never had to do this functionality. Now each template will look differently(colors/positioning) and possibly have different functionality available depending to the user. Questions I have are: - Can this actually be done with Borders? - As a separate Border "template" will be created per user, how does one organize their information and locate the particular Border, i.e. Class.forName( "com.xxx.app.wicket.template.r" + user.getId() + ".LoginBorder" ).newInstance(); - Are there any working examples that are available? The Border example via the Wicket Examples is pretty light. Thanks - Doug -- View this message in context: http://www.nabble.com/Struts-Tiles-to-Wicket-tf4845783.html#a13863837 Sent from the Wicket - User mailing list archive at Nabble.com. --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
