For now, everything we do in VertxMVC is blocking (reflection stuff).
In the future (see #4 ) there could be async stuff => VertxMVC should return Future<Void>, especially if users bootstrap from their own verticle.
Also, keep the reflection stuff and route reflection discovery out of this class. This class should only be a conductor for every kind of bootstrapping stuff :
routes by reflection
template handlers instantiation
database / ORM startup/config (if we implement the model layer)
loading fixtures
...
=> it needs to be refactored properly (and create a package named bootstrap)
aesteve
commented
9 years ago
For now, everything we do in VertxMVC is blocking (reflection stuff).
In the future (see #4 ) there could be async stuff => VertxMVC should return
Future<Void>, especially if users bootstrap from their own verticle.Also, keep the reflection stuff and route reflection discovery out of this class. This class should only be a conductor for every kind of bootstrapping stuff :
=> it needs to be refactored properly (and create a package named bootstrap)