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

Issue 466: Expose plugins for HttpInterceptorPipeline #475

Conversation

mikkokar
Copy link
Contributor

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 from plugins.all section.

When started programmatically:

  • Can be started only in the old application router mode.
  • All plugin factories passed to StyxServerComponents.Builder.pluginFactories() are loaded into the pipeline, in the order of appearance.

@mikkokar mikkokar merged commit 2fe8763 into ExpediaGroup:master Oct 10, 2019
@mikkokar mikkokar deleted the issue-466-plugins-for-backwards-compatibility-mode branch October 10, 2019 14:16
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.

2 participants