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: domain of c1vamsi1c@gmail.com designates
 64.233.182.202 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:references;
        b=IXQiwahTeQHf04cWpyJVTkEub9TYodWjlvmCpGW/QuKH1A6UnpfX8cBR5ryyAGeupj5fdjguG2StHYgnmJueiimk34fEA32gNgzJH2/BXPQRnlr7H7UB72L6ye4wmDsTepWfVtTbkVdTlHq00Ndwp3SlK3FTUo57aZBIk4NtO2U=
Message-ID: <22d56c4d0511172121ya9cb05eg453ec075f006656f@mail.gmail.com>
Date: Fri, 18 Nov 2005 10:51:13 +0530
From: Vamsavardhana Reddy <c1vamsi1c@gmail.com>
To: dev@geronimo.apache.org
Subject: Re: Constructing deployment plans from Configuration GBeanData
In-Reply-To: <93f2c9dc32adcf68c02aa2c99a928089@yahoo.com>
MIME-Version: 1.0
Content-Type: multipart/alternative;
	boundary="----=_Part_998_11187052.1132291273430"
References: <22d56c4d0511160410t1d099c47g6522e1607ff56909@mail.gmail.com>
	 <5fe06e27c9131035126fcf8cb7075ddc@yahoo.com>
	 <22d56c4d0511170445t5969d296we2663aae3a3c4b2a@mail.gmail.com>
	 <93f2c9dc32adcf68c02aa2c99a928089@yahoo.com>

------=_Part_998_11187052.1132291273430
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

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 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 of
things, and I can avoid writing a configuration decompiler :o). But, then
will there be any instances where the user will not want the deployment pla=
n
to be stored in the server as is? Will "not want to store the deployment
plan in the config-store" be ever a users' reason for supplying deployment
plan as an external file to the deployer?

thanks
> david jencks
>
>

------=_Part_998_11187052.1132291273430
Content-Type: text/html; charset=ISO-8859-1
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline

<br><br><div><span class=3D"gmail_quote">On 11/17/05, <b class=3D"gmail_sen=
dername">David Jencks</b> &lt;<a href=3D"mailto:david_jencks@yahoo.com">dav=
id_jencks@yahoo.com</a>&gt; wrote:</span><blockquote class=3D"gmail_quote" =
style=3D"border-left: 1px solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8=
ex; padding-left: 1ex;">
<br>On Nov 17, 2005, at 4:45 AM, Vamsavardhana Reddy wrote:<br><br>&gt; If =
deployment plans are inside the archive (ear, war, etc.) they can<br>&gt; b=
e obtained from config-store. If the deployment plan is supplied as<br>
&gt; an external file to the deployer and if the original file is not<br>&g=
t; available, the only way to get any information on the configuration is<b=
r>&gt; from the Configuration GBeanData obtained from the kernel at runtime
<br>&gt; or from deserializing config.ser files under config-store. For<br>=
&gt; analyzing any problems after an application is deployed, deployment<br=
>&gt; plans will certainly be helpful.<br><br>If you think this is really v=
aluable information, I think a better
<br>approach is to store the plan(s) in a known location in the<br>configur=
ation so they may be retrieved directly.</blockquote><div><br>
I thought of this as an option because it will really simplify a lot of
things, and I can avoid writing a configuration decompiler :o).&nbsp;
But, then will there be any instances where the user will not want the
deployment plan to be stored in the server as is?&nbsp; Will &quot;not want
to store the deployment plan in the config-store&quot; be ever a users'
reason for supplying deployment plan as an external file to the
deployer?<br>
&nbsp;</div><br><blockquote class=3D"gmail_quote" style=3D"border-left: 1px=
 solid rgb(204, 204, 204); margin: 0pt 0pt 0pt 0.8ex; padding-left: 1ex;">t=
hanks<br>david jencks<br><br></blockquote></div><br>

------=_Part_998_11187052.1132291273430--