More and more web servers integrate OSGi in some way, allowing for very dynamic server-side modules. In contrast, GWT's modules are static and must be available at compile time. What I am looking for is a client-side complement to server-side OSGi modules. In its simplest form, this could work as follows:
- On the server: another OSGi module tells the framework about a client-side module and a client-side class it provides. On the client, one then loads the module and instantiates the class. This scenario currently faces the following obstacles: - Classes can currently only be instantiated statically, via constructor or by specifying a class literal to GWT.create(). - Modules cannot be packaged, deployed or loaded as an independent entity. Does this make sense? Any pointers or comments? Thanks! Axel -- 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.
