Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Enhance Repository Log4J Settings tool to support data refresh without page reload #94

Closed
AFaust opened this issue Jul 23, 2017 · 0 comments
Assignees
Milestone

Comments

@AFaust
Copy link
Contributor

AFaust commented Jul 23, 2017

FEATURE / ENHANCEMENT

Currently the Log4J Settings tool on the Repository-tier requires reloading of the page to apply changes to log level settings, to change of the display filter concerning unconfigured loggers, and to reset/add loggers. The inclusion of the stateful log snapshotting feature (#57) render this behaviour unsuitable to be used any longer. A page reload will disrupt the use of the snapshot feature and should be avoided. As a result, all operations that currently trigger a page reload must be refactored to work with asynchronous requests/updates.

@AFaust AFaust added this to the 1.0.0.0 milestone Sep 15, 2017
AFaust added a commit to AFaust/ootbee-support-tools that referenced this issue Sep 15, 2017
- fix admin handling of request / response content type
- standardise on add/removeClass or toggle for hidden handling
- remove formData-based logger web script as no longer required
@AFaust AFaust self-assigned this Sep 16, 2017
AFaust added a commit to AFaust/ootbee-support-tools that referenced this issue Sep 18, 2017
- fix admin handling of request / response content type
- standardise on add/removeClass or toggle for hidden handling
- remove formData-based logger web script as no longer required
AFaust added a commit that referenced this issue Nov 19, 2017
- fix admin handling of request / response content type
- standardise on add/removeClass or toggle for hidden handling
- remove formData-based logger web script as no longer required
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

1 participant