In response to the below blog post (by Ben Northrop) http://www.summa-tech.com/blog/2011/02/22/structuring-gwt-modules-for-large-applications
I set up a sample app which uses a dynamic login page. So if you want more control over a login page but don't want it as part of your main module, take a look and let me know of any comments and suggestions or questions. It is a simple app but may serve as an okay example.. Demo: http://gwt-advanced-login.appspot.com/ Code: https://github.com/ashtonthomas/GwtAdvancedLogin I have created a sample application which uses a separate LoginModule to handle any pre-authentication/login stuff. I have included two main modules Overview: You have two main module that you want to put behind a login and you want to have full GWT-Control over your login page. I have created a Login module which loads and will fire a quick rpc to check for an existing session (if so redirect). It will show a form to either login or register The web.xml defines two servlets for the two main modules and a servlet for the login module. The two main module servlets are very basic. All they do is check for an existing user (if yes: return an html page which points to ModuleX.nocache.js, Otherwise, return an html page the loads the login.nochache.js) The default welcome file will just load login. Check out the web.xml and the servlets and login (entry point) -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To post to this group, send email to [email protected]. To unsubscribe from this group, send email to [email protected]. For more options, visit this group at http://groups.google.com/group/google-web-toolkit?hl=en.
