I guess we have a strong vote turnout favouring services... I will be switching subsystems
to services as I validate them against the latest AS7 builds. And I agree with Heiko's
comment about JBossWeb, we do have a precedent there.
Thank you,
Stefan Negrea
----- Original Message -----
From: "Heiko W.Rupp" <hrupp(a)redhat.com>
To: rhq-devel(a)lists.fedorahosted.org
Sent: Friday, March 23, 2012 9:35:53 AM
Subject: Re: AS7 Subsystems, Service vs. Server
Am 22.03.2012 um 17:40 schrieb Stefan Negrea:
> Working on AS7 plugin, I noticed that most (but not all) of the AS7
> subsystems are configured as server resources. So what should new
> subsystems being added to the plugin be mapped to, service or
> server? It is a hard decision to take with no guidelines in place.
> Heiko suggested I should to ask for community feedback.
We do not have any guidelines at all here. So I have been advocating
as a rule of thumb for a long time
"if it is an subsystem like JBossWeb, HornetQ etc. " which has
resources below it, make it a <server> ; especially if those
could also work standalone.
> Or just go with one single type of resource for all subsystem?
> Should it be service or server?
I don't mind putting them all as services.
But this will also confuse the user, as in as4 (and 5) jboss web,
messaging and so are servers and now they would be services
And on the historic side this whole p/s/s thing has just been taken
from JON 1
--
Reg. Adresse: Red Hat GmbH, Technopark II, Haus C,
Werner-von-Siemens-Ring 14, D-85630 Grasbrunn
Handelsregister: Amtsgericht München HRB 153243
Geschaeftsführer: Mark Hegarty, Charlie Peters, Michael Cunningham,
Charles Cachera
_______________________________________________
rhq-devel mailing list
rhq-devel(a)lists.fedorahosted.org
https://fedorahosted.org/mailman/listinfo/rhq-devel