MODCLUSTER-720 Allow mod_cluster listener to register at <Service> le… #456
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…vel rather than <Server> level
|
I need to close this (the original repo was deleted trying to workaround github debepdabot auto-enablement bug) and will reopen rebased. |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
…vel rather than level
https://issues.redhat.com/browse/MODCLUSTER-720
The container even handler needs to handle sequence of events that are sent when the listener is on the level as opposed to only handling the chain of events on the level. The intention is to only register that service the listener is registered on thus a service stub that only filers that service is then passed around.