Out of band signaling from agent/plugin to server / user

Jay Shaughnessy jshaughn at redhat.com
Fri May 11 18:25:50 UTC 2012


Perhaps we could beef up ResourceError to handle things a bit more in 
this area.   We could consider making some changes to the actual entity 
or, maybe just
add some more ResourceErrorTypes that could also be handled in special 
ways by the GUI, like a banner message for a resource or somesuch.

On 5/11/2012 11:29 AM, Ian Springer wrote:
> Yeah, I was talking about the underlying data value. I agree about the 
> XML side.
>
> On 05/11/2012 11:08 AM, John Mazzitelli wrote:
>>> I would get rid of IMMEDIATE, and just interpret a null value for
>>> PropertyDefinition.activationPolicy as "the change will go into
>>> effect immediately".
>> Just to be clear, I think we should still allow for "immediate" as a 
>> valid explicit value for that attribute in the XML, even if you elect 
>> to use null under the covers. Usually when you see attributes in XML, 
>> they always give you all the available values, even the default ones. 
>> For example, for booleans, you rarely, if ever, see only "true" or 
>> only "false" as valid. If the default is "true", the XML still allows 
>> the attribute to be explicitly set to "true". Just wanted to make 
>> sure we were talking about the underlying data value and not the XML 
>> attribute value.
>> _______________________________________________
>> rhq-devel mailing list
>> rhq-devel at lists.fedorahosted.org
>> https://fedorahosted.org/mailman/listinfo/rhq-devel
>
>



More information about the rhq-devel mailing list