Re: [jboss-as7-dev] hold off ADDing AS7 children resources to another resource until a runtime state is reached for this resource?
Le 13 mars 2013 à 18:43, Brian Stansberry <brian.stansberry(a)redhat.com> a écrit :
The management resources do exist though. They represent
configuration,
which exists and needs to be manageable.
Is the problem with the various runtime-only attributes and operations
that are exposed by the resources? There's no mechanism to hide those in
the API or flag that they are unavailable if some condition doesn't hold
(e.g. some new attribute 'active' == true)?
yes, that's simpler this way: for each runtime attr and operations, I check whether
the underlying hornetq server is active.
if that's not the case, I ignore the read-attribute (returning undefined) and fail the
operations.
I also have to make sure that AS7 service depending on HornetQ (topic, queue and cf
services) are not started until it becomes active.
I install them in NEVER mode and switch them to ACTIVE if HornetQ server fails over and
becomes active.
thanks,
jeff
--
Jeff Mesnil
JBoss, a division of Red Hat
http://jmesnil.net/