Okay, I don't understand how this should work... So, you mean: 1. Requesting the application for example 'http://appname.appspot.com/ singnup?asdfghjkl' 2. A httpServlet gets this 3. The httpServlet makes anything on the html document 4. The html is called 5. In the OnModuleLoad this anything will be evaluated 6 According to this evaluation the right module will be loaded.
Is this right? On Apr 20, 1:03 pm, Jan Ehrhardt <[email protected]> wrote: > You can add a property (e. g. a Dictionary) to your host page. Your entry > point checks the property and loads the required module. Setting the > property is a task, the server has to do. > > I think, using one host page instead of two different pages with two > different URLs might be more efficient. > > Regards > Jan Ehrhardt > > 2010/4/20 Jochen Schnaidt <[email protected]> > > > > > Okay, I read the docs and understand most of it. Is it possiple to > > describe which sequence should be loaded by the URL? > > > I planed that 'http://appname.appspot.com'is the administration and > > 'http://appname.appspot.com/singnup?asdfghjkl' > > is the signup page for event 'asdfghjkl'. > > > I don't know if it is possible. My next step was to learn about > > servlet. But for a servlet I need a site to show my data, this is how > > I came to the 2nd page. I understand it this way, that code splitting > > mainly works on user events. So I need something like a switch in my > > onModuleLoad with the different splitpoints in the cases and the URL > > parameter in the statemant. > > > Is this right? Is it feasible? > > > On Apr 20, 11:17 am, Jan Ehrhardt <[email protected]> wrote: > > > In GWT 2.0 code splitting was introduced. You can have one big > > application, > > > that contains both modules. In the standard case you load your > > application > > > as before. In the registration case you can load a second module and use > > it. > > > This is much better than having two applications with different entry > > > points. It also allows you, to have some basic infrastructure, that's > > used > > > by both modules. So you can create a third module. > > > > If you design this correct, you'll get an extendable and modularized > > > application, that loads modules if required. That happens all in the same > > > host page, so no page reload. > > > > Regards > > > Jan Ehrhardt > > > > 2010/4/20 Jochen Schnaidt <[email protected]> > > > > > Hi all, > > > > > I have a question about the design of a GWT project. > > > > I am working on an application for registration to events based on GWT > > > > and GAE. The application consists of three modules: administration > > > > (create, edit an event and reporting), signup (registration of guests) > > > > and a ‘desktop’ for the people working on the desk. > > > > At the moment I am finishing the first part administration. It is a > > > > classical RIA based on a DockLayout on one webpage. What I need now is > > > > a second Webpage where I can send my guests to register them to an > > > > event. I read a lot about this in the community but never found an > > > > answer how to do it right. > > > > When I add a second Webpage to my project and add a second entry point > > > > to the XML everything dumps. > > > > Must I create a second GWT project or is it possible to integrate this > > > > functions in a separated part of the existing project? > > > > > Ideas, comments are welcome. > > > > > Thanks a lot, greetings Jochen > > > > > -- > > > > 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]<google-web-toolkit%[email protected]> > > <google-web-toolkit%[email protected]<google-web-toolkit%[email protected]> > > > > > . > > > > For more options, visit this group at > > > >http://groups.google.com/group/google-web-toolkit?hl=en. > > > > -- > > > 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]<google-web-toolkit%[email protected]> > > . > > > For more options, visit this group athttp:// > > groups.google.com/group/google-web-toolkit?hl=en. > > > -- > > 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]<google-web-toolkit%[email protected]> > > . > > For more options, visit this group at > >http://groups.google.com/group/google-web-toolkit?hl=en. > > -- > 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 > athttp://groups.google.com/group/google-web-toolkit?hl=en. -- 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.
