Java in cloud

When you try to release your app, using Android Studio, you are pointed to that info: http://tools.android.com/tech-docs/new-build-system/user-guide#TOC-Signing-Configurations Despite being correct, it is not accurate and it will take few moments to realize how to configure the signing in the correct way: android { compileSdkVersion 18 buildToolsVersion "17.0.0" defaultConfig { minSdkVersion 7 targetSdkVersion 16 } signingConfigs { release { storeFile file("../android.keystore") storePassword System.console().readLine("\n\$ Enter keystore password: ") keyAlias "edziecko" keyPassword System.console().readLine("\n\$ Enter key password: ") } buildTypes { release { signingConfig signingConfigs.release } } } }

In this chapter I will cover how to develop single-paged web applications using the techniques mentioned in title. Source code is available there:  https://github.com/bartprokop/bart-gae-poc/tree/version1 . Working application is available here . Problem: putting all pieces together. Vaadin is great tool for developing Web based business application. It uses GWT for rendering the server side kept UI structures. So basically the whole application - both UI and backend runs on the server, while browser merely renders it. One of the properties of Vaadin application is that UI state is always serialized and kept inside http session. This feature has it's cons and pros. If you correctly persist session, you can run application on a cluster and the app will survive the restart or outage of single node. But everything what is references by any GUI elements must implement java.io.Serializable. As such is necessary to ensure that by accident we will not serialize whole object graph to h...