public class LoggingDeploymentResourceProcessor extends Object implements DeploymentUnitProcessor
Note that in some cases the assumed logging configuration will be wrong. If a deployment is using a custom log manager, such as logback, the configuration reported on the deployment will be the assumed configuration.
Modifier and Type | Field and Description |
---|---|
static AttachmentKey<LoggingConfigurationService> |
LOGGING_CONFIGURATION_SERVICE_KEY
The attachment key used to attach the service.
|
Constructor and Description |
---|
LoggingDeploymentResourceProcessor() |
Modifier and Type | Method and Description |
---|---|
void |
deploy(DeploymentPhaseContext phaseContext)
Perform a single step in processing the deployment phase.
|
void |
undeploy(DeploymentUnit context)
Undo the deployment processing.
|
public static final AttachmentKey<LoggingConfigurationService> LOGGING_CONFIGURATION_SERVICE_KEY
public final void deploy(DeploymentPhaseContext phaseContext) throws DeploymentUnitProcessingException
DeploymentUnitProcessor
Data stored on the phase context only exists until the end of the phase. The deployment unit context
which is persistent is available via context.getDeploymentUnitContext()
.
deploy
in interface DeploymentUnitProcessor
phaseContext
- the deployment unit contextDeploymentUnitProcessingException
- if an error occurs during processingpublic final void undeploy(DeploymentUnit context)
DeploymentUnitProcessor
deploy()
; however, if
the deploy()
method added services, they need not be removed here (they will automatically be removed).
This method should avoid throwing exceptions; any exceptions thrown are logged and ignored. Implementations of this
method cannot assume that the deployment process has (or has not) proceeded beyond the current processor, nor can they
assume that the undeploy()
method will be called from the same thread as the deploy()
method.
undeploy
in interface DeploymentUnitProcessor
context
- the deployment unit contextCopyright © 2023 JBoss by Red Hat. All rights reserved.