Interface and Description |
---|
org.jboss.as.server.deployment.transformation.DeploymentTransformer |
org.jboss.as.server.mgmt.domain.ExtensibleHttpManagement
Experimental; may be removed or incompatibly modified in a future minor or major release
|
Class and Description |
---|
org.jboss.as.server.deployment.DeploymentModelUtils
Use
DeploymentResourceSupport from an attachment on the DeploymentUnit |
org.jboss.as.server.ExternalManagementRequestExecutor
may be removed at any time.
|
org.jboss.as.server.operations.ServerRestartRequiredHandler |
Field and Description |
---|
org.jboss.as.server.deployment.Phase.CONFIGURE_RESOLVE_BUNDLE
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.DEPENDENCIES_BUNDLE
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.DEPENDENCIES_BUNDLE_CONTEXT_BINDING
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.INSTALL_BUNDLE_ACTIVATE
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.INSTALL_WAB_DEPLOYMENT
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.INSTALL_WAB_SERVLETCONTEXT_SERVICE
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.Services.JBOSS_EXTERNAL_MODULE_SERVICE
use capability org.wildfly.management.external-module
|
org.jboss.as.server.services.net.NetworkInterfaceService.JBOSS_NETWORK_INTERFACE
use the org.wildfly.network.interface capability
|
org.jboss.as.server.ServerEnvironment.JBOSS_PERSIST_SERVER_CONFIG
for internal us only, may change or be removed at any time without notice
|
org.jboss.as.server.Services.JBOSS_SERVER_EXECUTOR
use capability org.wildfly.management.executor
|
org.jboss.as.server.ServerEnvironment.MODULES_DIR
has no useful meaning
|
org.jboss.as.server.deployment.Phase.PARSE_OSGI_BUNDLE_INFO
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.PARSE_OSGI_COMPONENTS
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.PARSE_OSGI_DEPLOYMENT
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.PARSE_OSGI_SUBSYSTEM_ACTIVATOR
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.PARSE_WAB_CONTEXT_FACTORY
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.POST_MODULE_WAB_FRAGMENTS
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.controller.descriptions.ServerDescriptionConstants.PROCESS_STATE |
org.jboss.as.server.deployment.Phase.REGISTER_BUNDLE_INSTALL
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.ServerEnvironment.SERVER_DEPLOY_DIR |
org.jboss.as.server.ExternalManagementRequestExecutor.SERVICE_NAME
may be removed at any time
|
org.jboss.as.server.suspend.SuspendController.SERVICE_NAME
Use org.jboss.as.server.Services.JBOSS_SUSPEND_CONTROLLER instead which gets the service name
via org.wildfly.server.suspend-controller capability
|
org.jboss.as.server.deployment.Phase.STRUCTURE_BUNDLE_SUB_DEPLOYMENT
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.STRUCTURE_OSGI_MANIFEST
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.STRUCTURE_OSGI_METADATA
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.STRUCTURE_OSGI_PROPERTIES
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.deployment.Phase.STRUCTURE_OSGI_WEBBUNDLE
there is no phase processing associated with this constant - it was used for OSGi integration
|
org.jboss.as.server.controller.resources.ServerRootResourceDefinition.TIMEOUT
Since Version 9.0.0, use suspend-timeout instead.
|
Copyright © 2022 JBoss by Red Hat. All rights reserved.