Use ServletContextInitializer for application initialization #132
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Hi,
This commit introduces a new
ServletContextListener
,ApplicationInitializer
, which offloads parts of the responsibilities fromEntryServlet
. TheEntryServlet
was both serving as Jersey entry point servlet, but also as handling application initialization.This is now done in the listener. The
ConfigurationFactory
is also throwing an exception when there is no configuration file, instead of printing tostderr
and later throwing aNullPointerException
.With these changes, it is easy to identify when the application fails to initialize. Which is useful when a WAR application is deployed to a platform like AWS Elastic Beanstalk.