Issue 466: Expose plugins for HttpInterceptorPipeline #475
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.
Description
This PR tweaks plugins loading so that the plugins will be available for
InterceptorPipeline
object.Specifically, when started as a stand-alone application:
plugins.active
server configuration attribute is now optional. It can be omitted when styx is started with the routing object engine.httpPipeline
attribute activates the new routing object engine over the current application router. In this case all plugins are loaded fromplugins.all
section.When started programmatically:
StyxServerComponents.Builder.pluginFactories()
are loaded into the pipeline, in the order of appearance.