Skip to content

Conversation

@VladimirKozulin
Copy link

Optimize AntPathMatcher instantiation

  • Extract AntPathMatcher to static final field in RestAuthorizedUrlsRequestMatcher
  • Extract AntPathMatcher to static final field in ReportAsResourceServerBeforeInvocationEventListener
  • Extract AntPathMatcher to static final field in ReportOidcResourceServerBeforeInvocationEventListener

Eliminate code duplication in reports-rest module

  • Create AbstractReportBeforeInvocationEventListener base class with common logic
  • Refactor ReportAsResourceServerBeforeInvocationEventListener to extend base class
  • Refactor ReportOidcResourceServerBeforeInvocationEventListener to extend base class

Improve logging by using SLF4J parameterized messages

  • RestJsonTransformations: use {} placeholder instead of string concatenation
  • ReportExecutionHistoryRecorderImpl: use {} placeholder for path logging
  • LocalFileStorage: use {} placeholders for file path logging
  • HtmlFormatter: use {} placeholders for fonts directory logging
  • JavaProcessManager: use {} placeholder for process list logging
  • LinuxProcessManager: use {} placeholder for process list and error logging
  • WinProcessManager: use {} placeholder for process list and error logging
  • OOServer: use {} placeholders for profile directory logging

…and improve logging

- Task 1: Optimize AntPathMatcher instantiation
  - Extract AntPathMatcher to static final field in RestAuthorizedUrlsRequestMatcher
  - Extract AntPathMatcher to static final field in ReportAsResourceServerBeforeInvocationEventListener
  - Extract AntPathMatcher to static final field in ReportOidcResourceServerBeforeInvocationEventListener

- Task 2: Eliminate code duplication in reports-rest module
  - Create AbstractReportBeforeInvocationEventListener base class with common logic
  - Refactor ReportAsResourceServerBeforeInvocationEventListener to extend base class
  - Refactor ReportOidcResourceServerBeforeInvocationEventListener to extend base class

- Task 3: Improve logging by using SLF4J parameterized messages
  - RestJsonTransformations: use {} placeholder instead of string concatenation
  - ReportExecutionHistoryRecorderImpl: use {} placeholder for path logging
  - LocalFileStorage: use {} placeholders for file path logging
  - HtmlFormatter: use {} placeholders for fonts directory logging
  - JavaProcessManager: use {} placeholder for process list logging
  - LinuxProcessManager: use {} placeholder for process list and error logging
  - WinProcessManager: use {} placeholder for process list and error logging
  - OOServer: use {} placeholders for profile directory logging
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant