Circumvent synchronization on the Tapestry Session object

[khituras]

Currently, the ElasticSearch and Neo4j result Futures are stored in the session. This poses a problem when the widgets should be able to asynchronously load their data and render as soon as their data is available. When a longer-running process accesses the Session first, all other data retrieval requests wait at the Session monitor. This can cause widgets to display the loading message longer than necessary.

[khituras]

Unfortunately, the issue still persists even with the use of the GePiDataService. It seems that it only works fine often by accident.