This aproach will not work, since after compiled GWT generates pure JavaScript.
You could do the following: 1- Create an JSP page (index.jsp) and use this page as your GWT hosted page. 2- When rendering the page, check the name of the module (not the name of the class) that you want to load. 3- Create one Module.gwt.xml file for each of the user interface that you want to load. 4- When renderinhg the script tag that loads your selection script, change the name of your selection script based on the information that you retreived from the datastore. This options generate lots of files in your GAE application, because each UI will be compiled independ of another, but its fast. Another option will be: 1- Write your GWT application with all the UI and only one entry point class. 2- Create an jsp and define a cookie with the name (not the classname, GWT doesn't have reflection) of the UI that you want to load. 3- Inside your onModuleLoad function, write a series of if's that will check this cookie and load the UI that you want. 4- Use the GWT.async (code-splitting) to load the UI that you want, this will cost another round-trip but will download much less code. If you don't do that, the browser will download all the code for all the UI. Hope it helps. -- André Moraes Analista de Desenvolvimento de Sistemas [email protected] http://andredevchannel.blogspot.com/ -- 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.
