plugin-architecture

问题 As it currently stands, this question is not a good fit for our Q&A format. We expect answers to be supported by facts, references, or expertise, but this question will likely solicit debate, arguments, polling, or extended discussion. If you feel that this question can be improved and possibly reopened, visit the help center for guidance. Closed 7 years ago . I'm writing a J2SE desktop application that requires one of its components to be pluggable. I've already defined the Java interface

问题 In Node.js I was able to make a WordPress clone rather easily using the EventEmitter to replicate and build a hooks-system into the CMS core, which plugins could then attach to. I now need this same level of extensibility and core isolation for my CMS written in and ported to Go. Basically I have the core finished now, but in order to make it truly flexible I have to be able to insert events (hooks) and to have plugins attach to these hooks with additional functionality. I don't care about

问题 I am creating an application which uses the Java Plugin Framework to load plug-ins and integrate them into the program. My question is: Is there any way to restrict certain operations (such as starting a new process) in the plug-ins? What I have in mind is something like Java WebStart, i.e when the application wants to access the FileSytem, the user is prompted whether or not to allow the action. I was thinking of maybe creating a security manager and, if so, how can I do that? 回答1: I suggest

问题 I'm trying to build a web app which supports plugins, the environment is Angular 2 (so far), Typescript 2.1 and Webpack 2. I have some extension points (slots) where plugins can draw their content in: basically I have a component which is capable of hosting some other component known at runtime (see "Mastering Angular 2 Components" chapter 10 for the idea, and SO + plunker on how compile and "draw" at runtime an Angular component) Here's what I want to achieve: // in plugin.service.ts

问题 I'm trying to build a web app which supports plugins, the environment is Angular 2 (so far), Typescript 2.1 and Webpack 2. I have some extension points (slots) where plugins can draw their content in: basically I have a component which is capable of hosting some other component known at runtime (see "Mastering Angular 2 Components" chapter 10 for the idea, and SO + plunker on how compile and "draw" at runtime an Angular component) Here's what I want to achieve: // in plugin.service.ts

问题 I'm trying to build a web app which supports plugins, the environment is Angular 2 (so far), Typescript 2.1 and Webpack 2. I have some extension points (slots) where plugins can draw their content in: basically I have a component which is capable of hosting some other component known at runtime (see "Mastering Angular 2 Components" chapter 10 for the idea, and SO + plunker on how compile and "draw" at runtime an Angular component) Here's what I want to achieve: // in plugin.service.ts

问题 I've an application which is basically a designer with preloaded controls where you can design your pages using the controls. I'm planning to release more and more controls in the future. I don't want to release a new build for newly added controls as it has its disadvantages. So I was thinking of addon/plugin kind of architecture where I just release the addon/plugin separately which they can install and get the controls inside the designer. Right now I'm using xml files as addons to specify

问题 I'm following Justin Slattery's Plugin Architecture tutorial and trying to adapt it for Razor, instead of WebForm Views. Everything else (controllers, plugin assembly loading, etc) seems to be okay. However, I'm not able to get embedded Razor views to work properly. When I try to browse to the "HelloWorld/Index", I get the following error: The view at '~/Plugins/MyProjectPlugin.dll/MyProjectPlugin.Views.HelloWorld.Index.cshtml' must derive from WebViewPage or WebViewPage<TModel>. The

问题 Let say we have a Spring bean: @Component class PluginsProviderImpl implements PluginsProvider { private final List<PluginInterface> plugins; public PluginsProviderImpl(List<PluginInterface> plugins){ this.plugins = plugins; } //... } The implementations of PluginInterface have runtime dependency with the core system and are provided externally. It is possible that sometimes, some of them are erroneous (e.g. their dependencies are missing). If there is a such an error while Spring context

问题 I have read this, MEF (Managed Extensibility Framework) vs IoC/DI but it is dated. Since then MEF was added to Core. When I look at MEF and the IoC in ASP.NET Core, I cannot tell a lot of differences for a plugin architecture. Both "wire-up" dependencies. If I wanted to create a plugin in a Core application using IoC (the built in IoC), why not just change my ConfigureService methods? Is that the same as decorating imports and exports in MEF? How is composition different here, in 2017 (close