Separation of concerns
The framework is based on the presentation model pattern which means that your views (JSP files) determine which presentation model to use (Java classes) to return underlying data (a Java class with repository data). Thanks to this you don't have to write business logic of your components in JSPs any more.
...
Data coming from repository can be automatically mapped to Java objects using built-in object-resource mapper (ORM)
Modularity and dependency injection (DI)
Slice is strongly based on the dependency injection and Guice
. Thanks to this you can let Guice to provide you some objects which are required by your class, instead of creating them and passed "manually". Read more about Guice and DI here.
...
However, you will still use OSGi bundles but inside your application bundles there will be Guice dependency injection framework.
Guice
If you haven't used Guice before, we strongly advise you to read at least these couple of pages from Guice documentation:
...