On Mon, Nov 3, 2008 at 6:55 PM, Deepal jayasinghe <[EMAIL PROTECTED]> wrote:
>
> > 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.
good point. Lets associate many extensions with a deployer as Sanjiva has
mentioned.
Here the main point I want to tell is that deployer has nothing to do with a
directory. For an example POJODeployer deployes either a .class or .jar
file. Where is that file is not relevant for that.
As I can see even the repository can be able to configure through Axis2.xml
as well.
<repository class="<class name>" >
<parameter name="" value=""/>
<repository>
This repository can be a file repository, url repository, WSO2 registry
repository. Then the repository class can read the files on the repository
and ask deployers to deploy them. (Since a deployer has only associated with
a set of extensions) But this may have limitations in the way we read the
files from different repositories.
> > 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.
Well now you can understand the problem of not having custom deployers at
the begining of Axis2. Then custom deployers has introduced as a solution
for this. So it is an improvement but not an underestimation of the
existing work. This is what currently happen as well. There are requirement
even can not be solved by current custom deployers so need to improve it.
thanks,
Amila.
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: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
--
Amila Suriarachchi
WSO2 Inc.
blog: http://amilachinthaka.blogspot.com/
