You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
This repository has been archived by the owner on Oct 30, 2019. It is now read-only.
Many build environments allow the server to dynamically restart on code changes. This is a great help in increasing development efficiency, but it would appear as though SwaggerSocket does not like to gracefully restart. This should be as simple as providing cleanup functionality in the Servlet disposal method. For a test case of usage simply create an SBT web project and issue the command: "~;container:start; container:reload /" which will reload the container upon code change.
The text was updated successfully, but these errors were encountered:
Sign up for freeto subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Many build environments allow the server to dynamically restart on code changes. This is a great help in increasing development efficiency, but it would appear as though SwaggerSocket does not like to gracefully restart. This should be as simple as providing cleanup functionality in the Servlet disposal method. For a test case of usage simply create an SBT web project and issue the command: "~;container:start; container:reload /" which will reload the container upon code change.
The text was updated successfully, but these errors were encountered: