You are viewing a plain text version of this content. The canonical link for it is here.
Posted to c-dev@axis.apache.org by Sanjaya Ratnaweera <sa...@wso2.com> on 2006/04/26 01:58:41 UTC
[Axis2] Archive based deployment model
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
[Axis2] Including headers, making it easy
Posted by Samisa Abeysinghe <sa...@gmail.com>.
As of now, If one wants to use OM or SOAP, he/she needs to include a
lengthy list of headers to use the APIs in the respective headers.
To help users with this, I propose that we have few main headers that
would reduce the number of inclusions required.
However, we already have, axis2_soap.h axis2_om.h etc. that define
constants.
I propose that we move those to axis2_soap_const.h axis2_om_const.h.
Then we can use axis2_soap.h, axis2_om.h as convenient headers.
Thoughts please....
Samisa...
Re: [Axis2] MTOM Server Side Working
Posted by Thilina Gunarathne <cs...@gmail.com>.
Wow.. Keep up the good work... :)
~Thilina
On 4/30/06, Samisa Abeysinghe <sa...@gmail.com> wrote:
>
> We have MTOM working on the server side as well. Can talk to the Java
> client.
> There are some limitations though. Those would be reported in Jira.
>
> Thanks,
> Samisa...
>
> Deepal jayasinghe wrote:
>
> >WOW , great work !!!!!!!!!
> >
> >Samisa Abeysinghe wrote:
> >
> >
> >
> >>We have the MTOM client side working with Java server side.
> >>
> >>Many thanks to valuable contributions by Kapila to help realize this.
> >>
> >>Samisa...
> >>
> >>
> >>
> >
> >
> >
> >
>
>
--
"May the SourcE be with u"
http://webservices.apache.org/~thilina/
http://thilinag.blogspot.com/
http://www.bloglines.com/blog/Thilina
Re: [Axis2] MTOM Server Side Working
Posted by Samisa Abeysinghe <sa...@gmail.com>.
We have MTOM working on the server side as well. Can talk to the Java
client.
There are some limitations though. Those would be reported in Jira.
Thanks,
Samisa...
Deepal jayasinghe wrote:
>WOW , great work !!!!!!!!!
>
>Samisa Abeysinghe wrote:
>
>
>
>>We have the MTOM client side working with Java server side.
>>
>>Many thanks to valuable contributions by Kapila to help realize this.
>>
>>Samisa...
>>
>>
>>
>
>
>
>
Re: [Axis2] MTOM Client Side Working
Posted by Deepal jayasinghe <de...@gmail.com>.
WOW , great work !!!!!!!!!
Samisa Abeysinghe wrote:
> We have the MTOM client side working with Java server side.
>
> Many thanks to valuable contributions by Kapila to help realize this.
>
> Samisa...
>
--
Thanks,
Deepal
................................................................
~Future is Open~
[Axis2] MTOM Client Side Working
Posted by Samisa Abeysinghe <sa...@gmail.com>.
We have the MTOM client side working with Java server side.
Many thanks to valuable contributions by Kapila to help realize this.
Samisa...
Re: [Axis2] Archive based deployment model
Posted by Sahan Gamage <sa...@wso2.com>.
Hi Deepal,
See my comments below.. they are just my thoughts ..
Deepal jayasinghe wrote:
>Hi Sanjaya;
>
>pls see my comments below;
>
>Sahan Gamage wrote:
>
>
>
>>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.
>>
>>
>>
>>
>+1 , you have to have the same structure as explodede one so arcive file
>should look like below;
> foo.aar
> META-INF
> services.xml
> compile code
>
>
>
>>- 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.
>>>
>>>
>>>
>>>
>great :)
>
>
>
>>> - Archives are in zip format.
>>> - Archives have an .aar extension.
>>> - Archives are extracted in to the services directory.
>>>
>>>
>>>
>>>
>do we need to do this , without extracting cant you load the lib and all
>
>
In C, I don't think there is a way to load a library from a zip (or from
any archive file) without exploding it. This especially matters in
windows platform.
Infact the .so file( or the .dll) we are gonna include inside the
service archive (.aar) itself is an archive. But unfortunately we can't
include additional stuff like xml files and additional libraries which
leads us to this approach
>
>
>>> - 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.
>>>
>>>
>>>
>>>
>>>
>Axis2 java does not expand the archive file and it can load the stuff.
>can you please tell me what do you mean by " Extracted files are deleted
>before exit"
>
>
Yes. I know. Java has the capability of loading the libraries from an
archive. But for the C ppl, we have to have the required files contained
in a directory and not in a zip file so that the library loader can load
it. So our approach is explode (extract) the zip file on the startup,
load the libaries and depending on the users choice delete the extracted
folders at the exit. Hope that is clear ....
>
>
>>>Thanks.
>>>
>>> ~sanjaya
>>>
>>>--
>>>http://sanjayar.googlepages.com
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>>
>>
>
>
>
>
- Sahan
Re: [Axis2] Archive based deployment model
Posted by Deepal jayasinghe <de...@gmail.com>.
Hi Sanjaya;
pls see my comments below;
Sahan Gamage wrote:
>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.
>
>
+1 , you have to have the same structure as explodede one so arcive file
should look like below;
foo.aar
META-INF
services.xml
compile code
>- 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.
>>
>>
great :)
>> - Archives are in zip format.
>> - Archives have an .aar extension.
>> - Archives are extracted in to the services directory.
>>
>>
do we need to do this , without extracting cant you load the lib and all
>> - 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.
>>
>>
>>
Axis2 java does not expand the archive file and it can load the stuff.
can you please tell me what do you mean by " Extracted files are deleted
before exit"
>>Thanks.
>>
>> ~sanjaya
>>
>>--
>>http://sanjayar.googlepages.com
>>
>>
>>
>>
>
>
>
>
--
Thanks,
Deepal
................................................................
~Future is Open~
Re: [Axis2] Archive based deployment model
Posted by Sahan Gamage <sa...@wso2.com>.
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
>
>