i'm thinking of changing the structure of applications further so that we can have a more normal inheritance hierarchy instead of extending HttpServlet directly.
this would do away with both IApplication and the need for ApplicationContext (an idea i had earlier today, which i hate)
the main change for users would be that they would always use wicket.protocol.http.WicketServlet and the parameter to that servlet would be the WebApplication subclass' name.
the benefit to wicket in the long term is that we can easily add methods to the base and extend functionality by overriding those methods. because wicket's HttpApplication class directly subclasses HttpServlet this is not currently possible.
it's one more step for users, but there is a big benefit to the organization of the project here.
when i originally wrote wicket, i didn't really forsee how big ApplicationSettings was going to get as a result of not having an Application base class.
i think its time to fix this finally...
------------------------------------------------------- The SF.Net email is sponsored by: Beat the post-holiday blues Get a FREE limited edition SourceForge.net t-shirt from ThinkGeek. It's fun and FREE -- well, almost....http://www.thinkgeek.com/sfshirt _______________________________________________ Wicket-develop mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/wicket-develop
