[jboss-jira] [JBoss JIRA] Resolved: (JBAS-9147) Deployment-related OperationHandler improvements

[James Perkins (JIRA)]

     [ https://issues.jboss.org/browse/JBAS-9147?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

James Perkins resolved JBAS-9147.
---------------------------------

    Resolution: Done


Fixed on commit https://github.com/jbossas/jboss-as/commit/dea0688de9be51992edfc137c4b40f4e5865227a

> Deployment-related OperationHandler improvements
> ------------------------------------------------
>
>                 Key: JBAS-9147
>                 URL: https://issues.jboss.org/browse/JBAS-9147
>             Project: JBoss Application Server
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: James Perkins
>             Fix For: 7.0.0.Beta3
>
>
> Primary goal is to eliminate the need for a separate "deploy" operation following an "add" for a deployment resource. Plus minor cleanups.
> In all cases, the output of the DescriptionProvider associated with the handler must be updated to match changes to the handler.
> org.jboss.as.server.deployment:
> DeploymentAddHandler
> a) After updating the model, if context.getRuntimeContext() != null and subModel.get(ENABLED).asBoolean() == true, 
>    deploy the deployment. See DeploymentDeployHandler for how to deploy
> b) Update StandaloneXml (in controller module) so it doesn't create a "deploy" operation at boot, since "add" will now deploy
> c) lesser priority: handle other ways of providing the deployment content, depending on what param users provided:
>    -- HASH (i.e. content already uploaded) -- this is already implemented
>    -- INPUT_STREAM_INDEX (i.e. stream is attached to OperationContext)   -- this is already implemented
>    -- BYTES (param value is a byte[] of content) -- see DeploymentUploadBytesHandler for how to store the content in the repo
>    -- URL (server is to read content from URL) -- see DeploymentUploadURLHandler for how to store the content in the repo
> DeploymentFullReplaceHandler
> lesser priority: handle other ways of providing the deployment content, depending on what param users provided
>                  Same details as for DeploymentAddHandler
> DeploymentRemoveHandler
> remove the existing if (model.get(ENABLED).asBoolean()) {...} branch; the code should always execute the current "else {...}" branch
> org.jboss.as.domain.controller.operations.deployment:
> DeploymentAddHandler
> lesser priority: handle other ways of providing the deployment content, depending on what param users provided
>                  Same details as for org.jboss.as.server.deployment.DeploymentAddHandler
> DeploymentFullReplaceHandler
> lesser priority: handle other ways of providing the deployment content, depending on what param users provided
>                  Same details as for org.jboss.as.server.deployment.DeploymentAddHandler

--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira