codahale/dropwizard — Issue #35: Rationalize object lifecycles
Author: codahale
Created: 2012-02-17 23:52:09+00:00
State: open
Labels: task

Because so much of Dropwizard is glue code, the way in which things are created, configured, and wired together could use a bit more love.

* Jersey servlet container
* enable/disable Jersey features
* swap out for a `GuiceContainer` or what have you
* Jackson factory/mapper
* add modules, etc. for `ConfigurationFactory` and `JacksonMessageBodyProvider`
* enable/disable features for specific instances (e.g., `ConfigurationFactory` needs to always reject unknown fields)
* `MetricsRegistry`/`HealthCheckRegistry`
* really starting to regret those static factory methods
* would make JRebel-style development reloads possible