Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: local policy)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
  s=s1024; d=yahoo.com;
  h=Received:Mime-Version:In-Reply-To:References:Content-Type:Message-Id:Content-Transfer-Encoding:From:Subject:Date:To:X-Mailer;
  b=ptDP2q7/NiGIPfvyIzEG00f/B7Fdn/KzRauvGDQEWWbjdaEA1zGZf1fXqmcJhr1TDVfb5OkPpZReGVwGegZdvvNNZb3VUb2xeLEdVAfopeohvzzjbWYKpKmlBKyunyWVF3MsRh4byFNOKz9JQ6tFyV4lnzaQt1rK/HocFTSjt2Q=
  ;
Mime-Version: 1.0 (Apple Message framework v622)
In-Reply-To: <22d56c4d0511172121ya9cb05eg453ec075f006656f@mail.gmail.com>
References: <22d56c4d0511160410t1d099c47g6522e1607ff56909@mail.gmail.com>
 <5fe06e27c9131035126fcf8cb7075ddc@yahoo.com>
 <22d56c4d0511170445t5969d296we2663aae3a3c4b2a@mail.gmail.com>
 <93f2c9dc32adcf68c02aa2c99a928089@yahoo.com>
 <22d56c4d0511172121ya9cb05eg453ec075f006656f@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Message-Id: <8188ba8dc92532609f153bd1272ea18b@yahoo.com>
Content-Transfer-Encoding: quoted-printable
From: David Jencks <david_jencks@yahoo.com>
Subject: Re: Constructing deployment plans from Configuration GBeanData
Date: Thu, 17 Nov 2005 23:08:49 -0800
To: dev@geronimo.apache.org


On Nov 17, 2005, at 9:21 PM, Vamsavardhana Reddy wrote:

>
>
> On 11/17/05, David Jencks <david_jencks@yahoo.com> wrote:
>> On Nov 17, 2005, at 4:45 AM, Vamsavardhana Reddy wrote:
>>
>> > If deployment plans are inside the archive (ear, war, etc.) they =
can
>> > be obtained from config-store. If the deployment plan is supplied =
as
>>  > an external file to the deployer and if the original file is not
>> > available, the only way to get any information on the configuration=20=

>> is
>> > from the Configuration GBeanData obtained from the kernel at =
runtime
>> > or from deserializing config.ser files under config-store. For
>> > analyzing any problems after an application is deployed, deployment
>> > plans will certainly be helpful.
>>
>> If you think this is really valuable information, I think a better
>> approach is to store the plan(s) in a known location in the
>> configuration so they may be retrieved directly.
>  I thought of this as an option because it will really simplify a lot=20=

> of things, and I can avoid writing a configuration decompiler :o).=A0=20=

> But, then will there be any instances where the user will not want the=20=

> deployment plan to be stored in the server as is?=A0 Will "not want to=20=

> store the deployment plan in the config-store" be ever a users' reason=20=

> for supplying deployment plan as an external file to the deployer?

Well, I think there will be few cases where the original deployment=20
plan will be unavailable from other sources, and I don't particularly=20
like including it in the configuration.  However, I don't think this=20
has much to do with the desirability of keeping the plan separate from=20=

the module you are deploying: I think this is always a good idea.  I do=20=

think that some people will want to conceal their plan and if we do=20
provide a way to include it in the configuration this choice must be=20
optional.

thanks
david jencks