Switched to oj gem for JSON
Added oj as dependency
replacing handler configs with function reference
Binding scope of function in handler config to component
Look for haml template in child class
Introduced server side caching for composition and client_class
fixed typo
Revert "Switched to oj gem for JSON"

This reverts commit 2117ca93b0fd2eccfe77c3f51c3d1e8a6d9579c2.
Revert "Added oj as dependency"

This reverts commit 68896e0ecfdebb32826765e5530f7f29267ecb73.
Removed caching for component instances
Revert "Removed caching for component instances"

This reverts commit ca10e05d218abf1e6534766b7fe9e2e92fa42177.
bumped version
Skip cors protection for rails 4.1

In rails 4.1 cors protection is more strict. But since
with netzke we need to generate the js file on the
fly we need to skip the verification altogether.

A better solution would be to somehow integrate the 
dynamic ext.css and ext.js-file into the asset
pipeline, and let it build by that. Normally it
does not change often, except during development.
Merge branch 'master-wupdiwup' into master-dldi

* master-wupdiwup:
  bumped version
  Revert "Removed caching for component instances"
  Removed caching for component instances
  Revert "Added oj as dependency"
  Revert "Switched to oj gem for JSON"
  fixed typo
  Introduced server side caching for composition and client_class
  Look for haml template in child class
  Binding scope of function in handler config to component
  replacing handler configs with function reference
  Added oj as dependency
  Switched to oj gem for JSON

Conflicts:
	lib/netzke/core/version.rb
Merge branch 'master-nathanvda' into master-dldi

* master-nathanvda:
  Skip cors protection for rails 4.1