anchor.diff:  
   == Conclusion
   
  -On the backend, it has become a lot simpler. JEE 7 just works. It's much simpler than it's predecessors. Most rough edges are gone.
  +On the backend, it has become a lot simpler. JavaEE 7 just works. It's much simpler than it's predecessors. Most rough edges are gone.
   For full disclosure: I work for Red Hat, so I stuck to their implementations whenever there was a choice.
   
   On the frontend however... there's just so much choice and so many trade-offs between the technologies,
  
positive.code: 
  == Backend
  
  Writing the backend turned out to be a breeze, using JEE 7 technologies:
  
  * *Plain Java* to model the *domain classes*, such as `Speaker`, `Room`, etc.
  * *JAXRS* to expose a *REST service* to serve data to the webUI.
  
negative.code: * *JsonReader* to import the talks data from the http://cfp.devoxx.be/api[Devoxx CFP API] which is then transformed to our domain classes.
  ** I didn't use JAXRS to read that REST stream, because JsonReader gives me a DOM approach to the data,
  which I then directly map to our domain classes, without having to model their domain class too (which have no further use to us).
  ** Thanks to Arun and the https://github.com/javaee-samples/javaee7-samples[JavaEE 7 samples] to point me in the direction of the right tech for the job.
  * *OptaPlanner* to optimize the schedule
  ** This was also very easy to use for me ;)
  ** For more info, see the http://www.optaplanner.org[OptaPlanner documentation].
  