WildFly Modular Service Container: Difference between revisions
No edit summary |
(→API) |
||
| (27 intermediate revisions by the same user not shown) | |||
| Line 1: | Line 1: | ||
=TODO= | |||
<font color=red> | |||
'''TODO''' parse this https://developer.jboss.org/wiki/AS7InternalArchitectureOverview | |||
</font> | |||
=External= | |||
* AS7 Internal Architecture Overview https://developer.jboss.org/wiki/AS7InternalArchitectureOverview | |||
* Extending JBoss AS 7 https://docs.jboss.org/author/display/AS72/Extending+JBoss+AS+7 | |||
=Internal= | =Internal= | ||
* [[WildFly#Subjects|WildFly]] | * [[WildFly#Subjects|WildFly]] | ||
* [[WildFly Class Loading]] | |||
=Relevance= | =Relevance= | ||
| Line 14: | Line 21: | ||
=Overview= | =Overview= | ||
The JBoss Modular Services Container (MSC) is | The JBoss Modular Services Container (MSC) is a concurrent state machine. It dynamically analyzes the dependencies between all services and attempts to start as many as it can at the same time, while still adhering to the dependency relationship requirements. MSC implements new algorithms for checking module and service dependencies at deploy and run time, such that only the services that are needed are loaded and started, and when no longer needed unloaded. This makes unnecessary "slimming" a configuration to get a minimal memory footprint and start time. | ||
[[WildFly Class Loading|Modular class loading]] is at the core of MSC. | |||
Application server functionality, such as messaging or handling HTTP requests, is implemented in ''extensions'' to the MSC core. | |||
=Version= | =Version= | ||
| Line 24: | Line 35: | ||
=Source= | =Source= | ||
https://github.com/jboss-msc | {{External|GitHub: https://github.com/jboss-msc}} | ||
{{External|Maven Repository: https://repository.jboss.org/nexus/content/repositories/releases/org/jboss/msc/jboss-msc/}} | |||
=Implementation Details= | |||
<blockquote style="background-color: #f9f9f9; border: solid thin lightgrey;"> | |||
:[[WildFly Modular Service Container Implementation Details|Modular Service Container Implementation Details]] | |||
</blockquote> | |||
=Programmatic Access= | |||
{{Internal|WildFly Modular Service Container Programmatic Access|Programmatic Access}} | |||
=API= | |||
{{Internal|WildFly Service API|WildFly Service API}} | |||
Latest revision as of 21:48, 1 March 2017
TODO
TODO parse this https://developer.jboss.org/wiki/AS7InternalArchitectureOverview
External
- AS7 Internal Architecture Overview https://developer.jboss.org/wiki/AS7InternalArchitectureOverview
- Extending JBoss AS 7 https://docs.jboss.org/author/display/AS72/Extending+JBoss+AS+7
Internal
Relevance
EAP 6.4
Overview
The JBoss Modular Services Container (MSC) is a concurrent state machine. It dynamically analyzes the dependencies between all services and attempts to start as many as it can at the same time, while still adhering to the dependency relationship requirements. MSC implements new algorithms for checking module and service dependencies at deploy and run time, such that only the services that are needed are loaded and started, and when no longer needed unloaded. This makes unnecessary "slimming" a configuration to get a minimal memory footprint and start time.
Modular class loading is at the core of MSC.
Application server functionality, such as messaging or handling HTTP requests, is implemented in extensions to the MSC core.
Version
18:18:23,208 INFO [org.jboss.msc] (main) JBoss MSC version 1.1.5.Final-redhat-1
Source
- GitHub: https://github.com/jboss-msc