There are a few ways in which you can achieve this. *Create multiple modules * Works well; but increases build time.
*Single module, use code splitting* Use only a single module, but use code splitting such that when you access Application B you don't end up downloading the code for Application A. This requires some work, but will pay off in the long run. In the discussion thread you referenced, code splitting is not an option because application B happens to be an Admin area and you don't want an unauthenticated user to see the js code for admin ui. In your case, this is not an issue, and hence code splitting is a better option. --Sri 2009/12/28 Yousef.Ghandour <[email protected]> > I noticed that there is a couple of old posts regarding this issue, > and I need an answer for which way to consider. In my situation, I > have an application A, and another sub application B. Application B > will be used by Application A, however, application B is a stand alone > application and could be started alone with out Application A. > > Can I use the multiple entry points introduced in this article? > http://zenoconsulting.wikidot.com/blog:16#toc2. > Is there a better way to do it? If other posts answer this, please let > me know. > > Thanks > > -- > > 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 at http://groups.google.com/group/google-web-toolkit?hl=en.
