Separating routing and component creation.

This will make sense when we add actual fetching of data from the server. Then we need to first route match, then fetch data for that route, then actually render the component.
jshttp stuffs
Adding actual routing and an actual HTTP API to get data.

* Both browser and backend uses the same API to get data.
* js-http-client is a Java class that is accessible from nashorn, that is used to fetch data from the API.
* We remove notFound from the app.js routing, the point of the routing is to return null if a given URL is not found so we can know if the url actually matches something.
Merge branch 'master' of github.com:augustl/react-nashorn-example