Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (asf.osuosl.org: domain of davanum@gmail.com designates
 64.233.162.200 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=DNtRXxZfWVurrXopHuxCTIU74bPxxFlgQhLjHTCM4ZQubP2IVmnIqgSeK8nAEYyk/36dHDHvBsdhp7/PFhYe54r8qv0rUMfuoVEWAcOlQRsxoxbqtsJxj5UTybso+fdVYl2QoiFdX7P4zJjpviEWMvJyoXxBKFPPw4HzqNXwDBU=
Message-ID: <19e0530f0605071409r1720c9aaya156db9166fabe9c@mail.gmail.com>
Date: Sun, 7 May 2006 17:09:10 -0400
From: "Davanum Srinivas" <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-dev@ws.apache.org
Subject: Re: [Axis2] Management system - persistent configuration
In-Reply-To: <80592d5b0605071031s4b1b3353xa4649d3842ae2248@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <80592d5b0605071031s4b1b3353xa4649d3842ae2248@mail.gmail.com>

+1 to #1. Let's see how it works then decide on #2.

thanks,
dims

On 5/7/06, Chathura Ekanayake <cce.axis@gmail.com> wrote:
>
>
> Hi,
>
> I am implementing a mechanism to make the axis2 configurations persistent
> after system restarts.
>
> This is done by exporting the whole configuration as an xml file and load=
ing
> it after the restart.
> This can be done by two methods.
>
> (1) A remote management application can retrieve the configuration xml an=
d
> save it in the local machine. Then it can apply that configuration back t=
o
> the remote engine after the restart. (of course, the management applicati=
on
> can apply the retrieved configuration to any remote engine)
>
>
> (2) Axis2 engines can save its entire configuration in thier local disk a=
s
> an xml file (e.g. in WEB-INF\conf folder). Then the management system can
> read and apply that configuration at the startup.
>
>
> In this way, we can make the configuration made via web admin or the
> management API persistent after the system restarts.
> I have already implemented method (1) and currently working on method (2)=
. I
> think we can have both of them active at the same time.
> Please give your ideas about this.
>
> Regards,
>
> Chathura.


--
Davanum Srinivas : http://wso2.com/blogs/