axis-c-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Sahan Gamage <sa...@wso2.com>
Subject Re: [jira] Created: (AXIS2C-54) include files in src folders
Date Mon, 06 Feb 2006 03:57:54 GMT
Samisa Abeysinghe wrote:

> Damitha Kumarage wrote:
>
>> Hi,
>> nabeel yoosuf (JIRA) wrote:
>>
>>> include files in src folders
>>> ----------------------------
>>>
>>>         Key: AXIS2C-54
>>>         URL: http://issues.apache.org/jira/browse/AXIS2C-54
>>>     Project: Axis2-C
>>>        Type: Bug
>>>  Components: core/description     Versions: M0.3    Environment:
>>> windows
>>>    Reporter: nabeel yoosuf
>>>
>>>
>>> axis2_wsdl_compopent.h refers to description/axis2_description.h
>>> axis2_phase_holder.h refers to wsdl/axis2_wsdl.h
>>> axis2_transport_in_desc.h refers to
>>> transport/axis2_transport_receiver.h
>>> axis2_transport_out_desc.h refers to transport/axis2_transport_sender.h
>>>
>>> These header files should be moved to include dir.
>>>  
>>>
>> We need to restructure the header files according to the following.
>> * All the header files which are used internally by the axis2 engine
>> should be moved to respective folder structure.
>> * All the headers used by axis2 application/extenstion developers
>> should remain at include folder
>>
>> According to this scheme I suggest to keep following header files in
>> the include folder.
>> * All the header files related to modules/utility.  Also all the
>> header file currently in modules/util ex:default_log.h
>> and              default_string.h should be moved to include folder
>> * All OM related header files
>> * All clientapi related header files
>> * All transport related header files
>
>
> Do we need all transport headers?
>
>> * All soap related header files
>> * All message receiver header files
>>
> I think what the user needs is OM, SOAP, msg_ctx and client/server API.
> Do we need to expose the rest?
>
>> All other header files will be moved/remain at respective folders
>>
>> Now regarding the dll's we provide in binary distro
>> We will distribute following dll's separately in binary distro
>>
>> axis2_soap
>> axis2_om
>> axis2_util
>> axis2_core
>> axis2_wsdl
>> axis2_http_sender
>> axis2_http_receiver
>> axis2_http_transport
>
>
> Whay cant we have a single transport.so? Why we have to have sender
> and receiver seperate?
>
>>
>> note:
>> 1. axis2_util should be separate because user should be able to
>> replace it dynamically with his own implementation.
>
>
> Why does someone need to implement util? What are the cases?
>
>> 2. axis2_core consists all source in modules/core folder.
>> 3. axis2_soap should be separate because transport writers and
>> receiver writers need it
>
>
> Samisa...
>
>>
>> Please give your thoughts regarding this to proceed with
>> thanks
>> damitha
>>
>>
>>
>
>
To answer the question about the transport ... users should be able to
define their own senders and recivers seperately even in the same
transport ... for example a user can use simple_axis_server as the
reciever and a libcurl client as the sender. These should be loaded by
the class loader, not in compile time. So seperate .so files are requred
for the loading process to happen. The common transport specific utils
are defined in axis2_whatever_transport.so, so both sender and reciever
can use them.


- Sahan

Mime
View raw message