Running the application should now result in an application that looks like Figure 4-10.
When you deploy this application to App Engine, it will also deploy the required
supporting Flex files for you.
Many popular Java libraries and frameworks run on App Engine. Google doesn't
officially support these projects but it does take a community-oriented approach to
compatibility. There is an active and vibrant community dedicated to interoperability
of these projects. While some frameworks work with minor configuration changes,
others fail due to App Engine restrictions or unsupported classes.
In this chapter you built three applications using various technologies and
frameworks. Out of the box App Engine uses servlets and JSPs for web applications.
You built a small telesales application that used JSPs for the views, simple POJOs for
the model, and a single servlet for the controller. The application used Bigtable to
store and retrieve data with the JDO API.
You also created an application using the Spring MVC framework. The
application was light on actual functionality but was developed to show the best
practices and configuration needed to run on App Engine.
Your last application was developed using Adobe Flex for the front-end and using
GraniteDS for the remoting protocol. Remoting is much quicker and more efficient
than using XML across the wire and allows Flex applications to directly invoke remote
Java object methods and consume the return values natively. We walked through the
client-side MXML and ActionScript code development as well as the server-side. We
also took an in depth look at the server configuration to provide interoperability with
In our next chapter you'll actually start building your demo application. We'll
explore the functional as well as technical requirements and start developing the
front-end using Google Web Toolkit.