]
Brian Stansberry updated AS7-385:
---------------------------------
Fix Version/s: 7.1.0.CR1
(was: 7.1.0.Beta1)
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: Scott Stark
Priority: Critical
Fix For: 7.1.0.CR1
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: