[jboss-as7-dev] Expressions (Detyped API document feedback)

[Jason T. Greene]

On 1/6/11 7:31 AM, David M. Lloyd wrote:
> On 01/06/2011 04:42 AM, Kabir Khan wrote:
>>
>> On 6 Jan 2011, at 08:39, Max Rydahl Andersen wrote:
>>
>>>>>>>> 2) If there is significant benefit, how can we model this using the
>>>>>>>> simpler type system?
>>>>>>>
>>>>>>> Easy - I can add a PROPERTY_EXPRESSION type which attempts to resolve
>>>>>>> the expression when you call asString()/asInt()/etc. (toString() would
>>>>>>> return the expression).
>>>>>>>
>>>>>>
>>>>>> This would need to be done on the server side and the calculated result
>>>>>> shipped to the client.
>>>>>
>>>>> I'm not sure this is really necessary.  I'd think we'd have runtime
>>>>> operations available to query the actual values in use for these kinds
>>>>> of things; I think for regular model queries the user would want to read
>>>>> back the expressions only.
>>>>>
>>>>
>>>> This is true. The client can decide how to handle this themselves.
>>>> Simply returning PROPERTY_EXPRESSION from ModelNode.getType() is enough
>>>> to tell the client that the value needs to be resolved; they can decide
>>>> what to do with that information.
>>>
>>> How would a client resolve the expression ? Or rather - how could the client get the effective value of the property as seen by the server ?
>>
>> A 'query-property' operation?
>
> Yeah, or like I mentioned, maybe a flag to the "read" operation saying
> "give me this model node from server X with all properties resolved".
>

The big problem is this information is just informative. You can't 
really do anything with it as the whole point is that the value is on 
the server and not the domain.

-- 
Jason T. Greene
JBoss, a division of Red Hat