Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (herse.apache.org: domain of davanum@gmail.com designates
 64.233.162.233 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:reply-to:to:subject:cc:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=DE6y/S/uYqRvOJVvnrukoxvfxvb9aUoir6gVhgLA8wfPhwSXsEtQYig1UBc7WdQM+RS+K3DDdtD9STaAfJ4a7kseAsFV/TxxWatnTgNq888F0S4zsJjF1g3jNgSp+93i6+n5ufiXZzDtq6zGQPP423WxXYOQchy0Ui7+UxOMW2w=
Message-ID: <19e0530f0702090412p1c4bb957mb4dea493f500751e@mail.gmail.com>
Date: Fri, 9 Feb 2007 07:12:00 -0500
From: "Davanum Srinivas" <davanum@gmail.com>
Reply-To: dims@apache.org
To: axis-user@ws.apache.org
Subject: Re: [Axis2] -New feature : Adding custom deployer
Cc: "axis-dev@ws.apache.org" <axis-dev@ws.apache.org>
In-Reply-To: <45CC0627.1070608@opensource.lk>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <45CC0627.1070608@opensource.lk>

Deepal,

Did you test this with app servers that don't explode the war? We
always seem to break that with any change in deployment. Other than
that, Huge +1 for this.

thanks,
dims

On 2/9/07, Deepal Jayasinghe <deepal@opensource.lk> wrote:
> Hi All;
>
> The BOF we had at the ApcheConUS 2006 I suggested the idea of supporting
> custom deployers into Axis2. The main reason with that was in Axis2 we
> can not easily deploy new file extension (as an example JavaScript ) ,
> and In JAXWS side they are doing all the initialization at the
> MessageReceiver level since they do not have a deployment plug point. So
> with this approach we have much more flexibility ,among them
>
> - If you do not like the directory name "services" and "modules" then
> you can easily changed that to whatever you like
> - If you do not like the .aar , .mar file extension you can easily
> change that to whatever you like
> - If you want make a javaScript into a AxisService (or Module) and you
> want to deploy that into a new directory inside the repository (let's
> say folder called "javaScript") you can easily do that.
> - If you want to deploy test file as a service, module, Transport or
> even Parameter you can do that
> - Among the most useful thing we can easily write a new Deployer to make
> Axis1 service into Axis2
>
>
> I spent last night and completed the new approach (I am very sorry for
> implementing the feature w.o letting know the community), which
> introduces a new Interface called "Deployer" with fore method. If you
> want to write a new Deployer then you need to implement that .
>
> I changed the current Deployment mechanism to work the new approach.
>
> With new approach if you want to add new Deployer, then the following
> are the steps;
> - First write a class implementing Deployer interface
> - Second add the following entry to to axis2.xml
> <deployer extension="aar" directory="service"
> class="org.apache.axis2.deployment.ServiceDeployer"/>
>
>
> I think this is one of the very cool features I added to Axis2 and hope
> no one will -1 on this , I will commmit the changes soon. If everything
> goes well we can keep the code else we can revert.
>
> here is my +1 for this feature as well as for commiting the code.
>
> Thanks
> Deepal
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: axis-user-unsubscribe@ws.apache.org
> For additional commands, e-mail: axis-user-help@ws.apache.org
>
>


-- 
Davanum Srinivas :: http://wso2.org/ :: Oxygen for Web Services Developers

---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org