[jboss-jira] [JBoss JIRA] (AS7-385) Deal with expression values in all operation handlers

[Brian Stansberry (JIRA)]

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

Brian Stansberry resolved AS7-385.
----------------------------------

    Resolution: Done


The infrastructure is in place for supporting expressions in any persistent configuration item and I'm satisfied with the places where we've chosen to make the model attributes support expressions. If a need is identified for adding more expressions, this can be done by filing JIRAs on a case by case basis.
                
> Deal with expression values in all operation handlers
> -----------------------------------------------------
>
>                 Key: AS7-385
>                 URL: https://issues.jboss.org/browse/AS7-385
>             Project: Application Server 7
>          Issue Type: Task
>          Components: Domain Management
>            Reporter: Brian Stansberry
>            Assignee: Brian Stansberry
>            Priority: Critical
>             Fix For: 7.1.0.Final
>
>
> Pretty much any simple value in a detyped operation can be of type ModelType.EXPRESSION instead something an OperationHandler might expect, like ModelType.STRING or ModelType.INT. All handlers need to deal with this fact.
> There are two main aspects to this:
> 1) Any parameter validation that goes on needs to account for the presence of expression values. Basically that means 
> a) accept the expression for storage in the model 
> b) call resolve() on the operation and use the resolved version for application to the runtime.
> c) re-validation of the resolved value may be necessary

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira