Mailing-List: contact axis-dev-help@ws.apache.org; run by ezmlm
Precedence: bulk
Reply-To: axis-dev@ws.apache.org
Received-SPF: pass (athena.apache.org: domain of deepalk@gmail.com designates
 74.125.46.157 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:user-agent:mime-version:to:subject:references
         :in-reply-to:x-enigmail-version:content-type
         :content-transfer-encoding;
        b=jWYOZ7EHo5hqHuZ6Um3F0SklkM6DKanvco4p9cbSaAafIsHaDzyLpEpybJ4NiP3WzX
         Mrgx90AY9Gq6EwItCJB2QcL6Ngt5VJ98daBqaqMysc91btFliaoR6rEUdmNGZLezEomb
         bt+cTH0onNFXbaD0NBJXa1JrYRSEEOp9DUKuU=
Message-ID: <490EFBD4.6020003@gmail.com>
Date: Mon, 03 Nov 2008 08:25:40 -0500
From: Deepal jayasinghe <deepalk@gmail.com>
User-Agent: Thunderbird 2.0.0.17 (Windows/20080914)
MIME-Version: 1.0
To: axis-dev@ws.apache.org
Subject: Re: Multiple deployers in axis2.xml
References: <5eb405c70810281420p59520b57x644548a655c38c44@mail.gmail.com>
	 <5eb405c70810300818w6f2f5128w3abf9ec070beebe6@mail.gmail.com>
	 <490E6EBE.6010509@opensource.lk>
 <60708f4b0811030103m5ae8f582xa8b9e1ba0872d656@mail.gmail.com>
In-Reply-To: <60708f4b0811030103m5ae8f582xa8b9e1ba0872d656@mail.gmail.com>
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit


> we can do some thing like that Jboss does. In Jboss if you want to
> deploy a web application either it should be put as .war file or under
> a directory of which name ends with .war .
>
> i.e in axis2 point of view either it should be bar.aar file or bar.aar
> directory.
>
> In my point of view always deployer should only map to an extension.
-1 , if you think the POJO deployer it can handle both .class files and
.jar files , so are you saying thats a problem.  If we have the
flexibility and if we doing that for a long time without any problem,
then we should continue to keep it as it is.
> In the above way it can support both expanded and single file modes.
Hehe , seems like you are not happy with the current way  , I do not
know whether you know about the deployment mechanism we had before the
deployer concept , and do you know how much of work JAX-WS people did to
deploy their services. FYI , at Apachecon US 2007 we had a BOF session
and their they mentioned what they are doing and the difficulties of the
process , so as  solution to that problem I introduced the idea of
deployer , and whether you agree with me or not , it made the deployment
so flexible and more extensible. And I do not see a any issues with that
other thane the issue that Jarek mentioned.

Thank you!
Deepal

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