1) Configure dependencies in BuildConfig.groovy.

 
compile('com.googlecode.ehcache-spring-annotations:ehcache-spring-annotations:1.2.0'){
    excludes 'ehcache-core', 'slf4j-api'
}
 

2) Configure spring resources.xml. We are using proxy-target-class="true" option to avoid JdkDynamicAopProxy ClassCastException problem.

 
<?xml version="1.0" encoding="UTF-8"?>
<beans xmlns="http://www.springframework.org/schema/beans" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:context="http://www.springframework.org/schema/context" xmlns:ehcache="http://ehcache-spring-annotations.googlecode.com/svn/schema/ehcache-spring"
    xsi:schemaLocation="http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-3.0.xsd
        http://www.springframework.org/schema/context http://www.springframework.org/schema/context/spring-context-3.0.xsd
        http://ehcache-spring-annotations.googlecode.com/svn/schema/ehcache-spring http://ehcache-spring-annotations.googlecode.com/svn/schema/ehcache-spring/ehcache-spring-1.1.xsd">
 
    <ehcache:annotation-driven proxy-target-class="true" />
 
    <ehcache:config cache-manager="cacheManager">
        <ehcache:evict-expired-elements interval="60" />
    </ehcache:config>
 
    <bean id="cacheManager" class="org.springframework.cache.ehcache.EhCacheManagerFactoryBean"/>
 
</beans>
 

3) Configure Ehcache in ehcache.xml.

 
<?xml version="1.0" encoding="UTF-8"?>
<ehcache xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
         xsi:noNamespaceSchemaLocation="ehcache.xsd">
 
    <diskStore path="java.io.tmpdir"/>
 
    <defaultCache
            maxElementsInMemory="10000"
            eternal="false"
            overflowToDisk="false"
            timeToIdleSeconds="300"
            timeToLiveSeconds="300"
            diskPersistent="false"
            diskExpiryThreadIntervalSeconds="120"
            memoryStoreEvictionPolicy="LRU"
            />
 
    <cache name="cacheableService"
           maxElementsInMemory="30000"
           eternal="false"
           overflowToDisk="false"
           diskPersistent="false"
           timeToLiveSeconds="86400"
           timeToIdleSeconds="0"
            />
 
</ehcache>
 

4) Use annotations in code:

 
class CacheableService {
 
    @Cacheable(cacheName="cacheableService")
    public MyData getData() {
        ...
        return myData
    }
 
    @Transactional
    @TriggersRemove(cacheName="cacheableService", removeAll=true)
    public void updateData() {
        ...
    }
}
 

We started with JavaScript refreshing - quick review of JavaScript magick. As a exercise we got task to implement elements of Aspect Programming in JavaScript.

Next we jumped to NodeJS and I must say that this was the most interesting part of whole meeting. His callback approach provide really powerful way for creating server-side code. After theoretical part we started implementation of chat - part of online code editor that was ours goal on this meeting. It was rally amazing to see that the same library (Socket.IO) is used on client and server side, JSON is transparent for both sides and all was running in less than 15 minutes.

As last element we explore RingoJS - MVC Server framework. It wasn't impressive - yet another framework. Only interesting thing in it is possibility of Java libraries usage. But there is no "magic" that NodeJS is offering and there is a lot of much better frameworks around in any other language.

Whole meeting was really successful, it has given me wider look on server side JavaScript, and I am definitely recommending it any one who want to learn something interesting.

After quick warm-up with framework and GAE infrastructure I have created first snapshot of my application.  All was smooth and easy. The only problem was with page response time: it was taking even ~5s to get response. In logs I found this information:

This request caused a new process to be started for your application, and thus caused your application code to be loaded for the first time. This request may thus take longer and use more CPU than a typical request for your application.

Quick search through a mailing lists and I found information that GAE will utilize your instances, if they are not used (with in case of low traffic application is more than sure). There is solution to prevent that: you can buy Always On option, but at this moment it costs 9$/month. Its not much as for Java hosting solution, but well - its still more than PHP.

You can play in Biolab disaster to check how cool it is. I am over deep impression about it.

But despite these wins, and numerous loyal fans, Wave has not seen the user adoption we would have liked.

For me its quite strange: in my company we use Wave and it works very well and for sure there is lots of companies that are in the same position. Why they can keep it online like other closed products (like Google Notebook)? Did Google think that it will be competition for Twitter? What it mean "user adoption" for Google?

Lots of questions but there is on sure - for Novel Pulse it's good news.