Hi, I am +1 for this model. There are few suggestions: 1. Can we do the same for the modules as well. (.mar instead of .aar) 2. The user should be able to put a flag(may be in axis2.xml) whether to delete or not, the exploded directories at the exit. 3. The structure inside the zip file. Whether to zip the directory or the files/directories inside it. My personal view is that we should zip the contents of the service directory and not the directory itself. This way the users doesn't have a chance of naming the service directtory and the zip file in different names.
- Sahan Sanjaya Ratnaweera wrote: > Hi all, > > I'm implementing an archive based deployment model for Axis2 C. > > Here is the outline of how I am going to implement it: > > - Archives are placed in the "services" directory. > - Archives are in zip format. > - Archives have an .aar extension. > - Archives are extracted in to the services directory. > - Services are deployed using the same method used to deploy not > archived services since there's no diffrence between archived > and not archived services after extracting. > - Extracted files are deleted before exit. > > Thanks. > > ~sanjaya > > -- > http://sanjayar.googlepages.com > >
