Christian, Sorry I missed your gchat the other day. Most gServices are blocked at my office.
Thanks a lot, it was an interesting answer. Beyond GWT, I'm curious about > how are you managing dynamic ORM extensions, i.e. if you are using JPA, how > are you merging domain classes from several OSGi bundles. We have a totally isolated model to deal with the domain objects. module_B has its own Spring services running in the OSGi container that serves up the dynamic content for module_B and uses its own schema and JNDI connection pool. The static content (compiled GWT) for module_B is served up by the aforementioned fragment attached to the module_B context. This way module_B and module_A can be upgraded completely independently of each other. Of course there are some objects which are shared in the GWT codebase (DTO's). These are in a common library inherited by all the modules that use it. Because we use Maven and versioning, we don't have to update all consumers of the common library and can run multiple versions on multiple modules. There are some shared services that multiple modules use, but these are consumed via JSON and Autobean (have not tried RequestFactory yet) since GWT-RPC is compile dependent for each module. I hope that helps. Sincerely, Joseph -- You received this message because you are subscribed to the Google Groups "Google Web Toolkit" group. To view this discussion on the web visit https://groups.google.com/d/msg/google-web-toolkit/-/3ABRkvA6SDUJ. 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.
