Remove sequence-response handling dependence on message logging ON status
- Dominant language
- Java
- Stars
- 61
- Forks
- 12
- PR merge metrics
- No merged PRs in 30d
Description
_Sequence handling does not work_, when Message Logging is turned off. In this case the responses are not collected to the sequences, and stub response generation is not possible.
This is because turning on/off message handling is adding/removing relevant processors by `com.epam.wilma.core.toggle.message.MessageLoggingToggle` class, but extracting and storing the sequence response is in the `ResponseQueueListener` class, that works only when the processor is enabled.
Need to remove the sequence-response handling dependence on message logging ON status - that feature should be always enabled.
Contributor guide
No contributing guide indexed for this repository
Research direction
Start by reading com.epam.wilma.core.toggle.message.MessageLoggingToggle and ResponseQueueListener to trace how processors are enabled and how sequence responses are collected. Confirm the behavior with Message Logging turned off, then verify that sequence responses are still stored and stub response generation remains possible independently of message logging.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- java
- Domain
- backend
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100