In my case, the login page needs functionality shared with the regular app, so it is better to have a single module with two entry points. Anoher option is to divide it in three modules, login, app, shared- stuff and the first two inherit the shared-stuff.
On Aug 5, 6:42 am, Insano <[email protected]> wrote: > I am currently developing a tool using Spring Security and and have > two pages. One for the login and the other one for the actual tool. > Both pages are built with GWT. > > What would be the best practice here? Would a module per page make > sense? Or a simple module with two entry entry point classes? > > Thanks for any advice --~--~---------~--~----~------------~-------~--~----~ 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 -~----------~----~----~----~------~----~------~--~---
