Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: neutral (nike.apache.org: local policy)
Message-ID: <473967EA.5070906@apache.org>
Date: Tue, 13 Nov 2007 10:01:30 +0100
From: Jeff Genender <jgenender@apache.org>
User-Agent: Thunderbird 2.0.0.6 (Macintosh/20070728)
MIME-Version: 1.0
To: dev@geronimo.apache.org
Subject: Re: Distribution and start/stop of clustered deployments
References: <B7ACC817-A9F6-4488-B4D8-16790A8BABC6@optusnet.com.au>
 <47388ED9.7050000@apache.org>
 <5F7BA842-86D1-4EE1-864E-C32D02FF1A1F@optusnet.com.au>
 <47393951.1070602@apache.org>
 <DDF9F362-4900-4F9D-9D08-7F9266E0520F@optusnet.com.au>
In-Reply-To: <DDF9F362-4900-4F9D-9D08-7F9266E0520F@optusnet.com.au>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


Gianny Damour wrote:
> I hope we are not talking about the same thing. I am talking about a
> "deployment time" constraint and not a "runtime" constraint mandating
> that all the servers are reachable when an application is *deployed*.
> FWIW, such a constraint was also defined by WebLogic 7.0; from WebLogic
> 8.x+, this constraint was subsequently relaxed in order to allow the
> deployment to a sub-set of the cluster members - however, users can
> still enforce it if they want and partial deployments is not
> recommended. As previously said, it is trivial to implement a GBean to
> distribute a backed configuration to a server, which was not reachable
> upon deployment.

Yes I mean deployment time...

I don't see a difference.  Yes...I think a switch for "allor nothing" or
"deploy to those who can" would be a good feature to have.

Jeff