Ideally there would be something hanging off of the Resource entity that
flagged the Resource as needing a restart to pickup the latest config
update, and then somehow that flag would be automagically cleared once
the Resource was restarted. The latter would be easy to do if the
Resource was restarted via RHQ, but much harder if the underlying
managed resource was restarted outside of RHQ. One thing we could use
for the restart required flag would be a ResourceError - we could define
a new RESTART_REQUIRED ResourceError type.
This also relates to activation policy metadata on Configurations and
individual config properties, something we've talked about since config
was first implemented but never implemented. That is, in a config def in
a plugin descriptor, you could define a property's activation policy:
1) requires a Resource restart
2) requires a restart of the parent server or platform
3) immediate (this would be the default)
On 07/21/2011 04:25 PM, Heiko W.Rupp wrote:
Hi,
currently when writing a configuration, we can only return "success" or throw
an Exception on failure.
Is there a way to convey extra information on success?
Background: in as7 when e.g. changing the a port definition for the socket bindings, the
result on
success may be "reload required" that should be presented to the user
(actually, that should even be a badge in the resource tree until the reload is done).
Any ideas?
Heiko
--
Ian Springer
Principal Software Developer
JBoss Operations Network
Red Hat
ian.springer(a)redhat.com