Have you ever felt that your system could collapse like the house of cards? Has it ever happened to you that an OSGi component got unsatisfied and that caused a chain reaction? It can be hard to find the root cause when you see 50+ non-active components. In this talk, we will show, how these issues can be solved quickly so programming can be fun again.
In the first part of the talk we will introduce our component model that is based on the concept of Declarative Services. There are minor changes, the ones that allow us to handle large set of component graphs easily.
In the second part
- we will play a short game with the audience. One must cause a mistake in a large system while another developer (who did not see the change) must fix it.
- there will be a demo where we set up a complex Servlet Container with multiple Servlet Contexts, Servlets, and Filters via configuration.