Home

Welcome to the tvguide-sample-parent wiki!

Lessons learned during development:

GWT

RequestFactory

We tried to be very careful in terms of what code has access to which RequestContexts and RequestFactorys, but it seems to not matter, at least in our early examples. What does matter, however, is which Proxy types have access to which other Proxy types, and how far that tree spreads. Because Proxies can be loaded with sub-proxies (and sub-sub-proxies, etc) through the Request.with command at runtime, the compiler can't tell which types the server is going to send back, so it needs access to all possible reachable types. (see RequestFactory Instances for more info)

Gin

Split Points

Servlet Container

Guice

Servlets and Filters

Notes on the core data server

The tvguide-server project is not intended to be part of the sample code, but is instead a chance to try something new, and see if we can learn something from it.

This part of the app is using some very non-standard ways of doing things, but this should not affect how the rest of the project is put together. We've taken the approach of not providing service classes with methods that map to the requests the client might send, but instead providing Callables on the server for each method, and asking Guice to inject and prepare them for us. This has the downside of failing validation of the RequestContexts, requiring a small addition in how the custom ServiceLayerDecorator provides app-specific instances.