Dynamically Loaded Plugin Architecture
A method and architecture for using dynamically loaded plugins is described herein. The dynamically loaded plugin architecture comprises a parent context and a plugin repository. The parent context may define one or more reusable software components. The plugin repository may store one or more plugins. When a plugin is loaded, a child context may be created dynamically. The child context is associated with the plugin and inherits the one or more reusable software components from the parent context.
1 - 20 . (canceled)
21 . A system comprising:
a processor operable to generate a first software component, wherein:
one or more portions of code of the first software component are from a second software component,
the first software component is operable to generate a model that adds a feature to a host application, and
a violation is indicated if the model was previously generated.
22 . The system of claim 21 , wherein the first software component comprises executable code within an application.
23 . The system of claim 21 , wherein the first software component is operable on a hardware processor.
24 . The system of claim 21 , wherein the first software component is on a server.
25 . The system of claim 21 , wherein the first software component is operable to run independently from and concurrently with the second software component.
26 . The system of claim 21 , wherein the first software component is defined by an application programming interface (API).
27 . The system of claim 21 , wherein the first software component is uniquely identified by a version.
28 . The system of claim 27 , wherein a first version of the first software component is operable to run independently from and concurrently with a second version of the first software component.
29 . The system of claim 21 , wherein the first software component is stored in a container.
30 . A method comprising:
loading a first software component;
inheriting, by the first software component, one or more portions of code from a second software component;
generating, by the first software component, a model that adds a feature to a host application; and
triggering a violation if the model was previously generated.
31 . The method of claim 30 , wherein the method comprises executing code, on the first software component, within an application.
32 . The method of claim 30 , wherein the method comprises operating the first software component on a hardware processor.
33 . The method of claim 30 , wherein the method comprises operating the first software component on a server.
34 . The method of claim 30 , wherein the method comprises operating the first software component independently from and concurrently with the second software component.
35 . The method of claim 30 , wherein the method comprises defining the first software component by an application programming interface (API).
36 . The method of claim 30 , wherein the method comprises uniquely identifying the first software component by a version.
37 . The method of claim 36 , wherein the method comprises running a first version of the first software component independently from and concurrently with a second version of the first software component.
38 . The method of claim 30 , wherein the method comprises storing the first software component in a container.