WildFly Modular Service Container Implementation Details: Difference between revisions
Jump to navigation
Jump to search
| Line 9: | Line 9: | ||
:https://github.com/jboss-msc/jboss-msc/blob/master/src/main/java/org/jboss/msc/service/ServiceContainerImpl.java<br> | :https://github.com/jboss-msc/jboss-msc/blob/master/src/main/java/org/jboss/msc/service/ServiceContainerImpl.java<br> | ||
</blockquote> | </blockquote> | ||
=Programmatic Access= | |||
<font color=red> | |||
TODO: | |||
* Can I get a hold of the container, programmatically? Use/extend the code linked above. | |||
* Document API. | |||
* Document Maven dependencies. | |||
* jboss-deployment-dependencies. | |||
* Document ServiceContainerHelper, and the fact that getting the value of a service starts it. | |||
* Document that the service needs to be started in order to getValue(), and if I get null for getValue(), the service is probably not started. | |||
</font> | |||
Latest revision as of 04:54, 13 January 2017
Internal
ServiceContainer
Programmatic Access
TODO:
- Can I get a hold of the container, programmatically? Use/extend the code linked above.
- Document API.
- Document Maven dependencies.
- jboss-deployment-dependencies.
- Document ServiceContainerHelper, and the fact that getting the value of a service starts it.
- Document that the service needs to be started in order to getValue(), and if I get null for getValue(), the service is probably not started.