Hi, There is a problem with using different Wicket related projects in one application, because in many cases each project defines its own implementation of WebApplication class (and sometimes WebSession too). For example: - wicket-spring: SpringWebApplication - wicket-auth-roles: AuthenticatedWebApplication - wicket-swarm: SwarmWebApplication etc...
If I want to use wicket-spring and wicket-swarm, there is a problem: from which class should I extend my application class: SpringWebApplication or SwarmWebApplication? So I think it is not a good "pattern" to implement such things by extending an application and a session base classes, because this closes the door for integration different projects into one application. -- Daniel ------------------------------------------------------------------------- This SF.net email is sponsored by DB2 Express Download DB2 Express C - the FREE version of DB2 express and take control of your XML. No limits. Just data. Click to get it now. http://sourceforge.net/powerbar/db2/ _______________________________________________ Wicket-user mailing list Wicket-user@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/wicket-user
