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 Sahan Gamage <sa...@wso2.com> on 2006/05/02 18:33:24 UTC
[Axis2]Organizing the error codes
Hi all,
I am planning to reorganize the error codes in error.h as well as in the
error.c. Following is the option that comes into my mind about the way I
am going to organize the codes.
The directory hierarchy of the modules directory of current axis2c
implementation is as follows.
modules
|
|-core
| |-addr
| |-clientapi
| | |-diclient
| |-context
| |-deployment
| |-description
| |-engine
| |-phaseresolver
| |-receivers
| |-transport
| | |-http
| | | |-receiver
| | | |-sender
| | | | |-ssl (will be there soon)
| | | |-server
| | | | |-apache2
| | | | |-simple_axis2_server
| |-util
|-mod_addr
|-platforms
| |-unix
| |-windows
|-util
|-wsdl
|-xml
| |-attachments
| |-om
| |-parser
| | |-guththila
| | |-libxml2
| |-soap
Note that I have specifically ignored woden and xml_schema since we are
not finalized the status of these projects (eg: whether to separate them
as new projects)
So the order of the error codes will be the order we get by flattening
the above hierarchy.
Next is the convention of the error codes. I assume the convention
proposed by samisa in AXIS2C-67.
Also there are lot of error codes which doesn't have descriptions along
with them. If the respective authors can update the error.h with the
comments I can update the descriptions in the error.c file. Pls take
some time to do that before the next release.
Comments are welcome for the above proposal
- Sahan
Re: [Axis2]Organizing the error codes
Posted by Sahan Gamage <sa...@wso2.com>.
Hi All,
I have grouped all the error codes in the axis2_error.h and
modules/util/error.c. But some of the error codes are missing their
associated description. I would appreciate if all the respective
developers take some time and fill the missing descriptions. These are
marked as *TODO ADDCOMMENT*. Please update the respective description in
the modules/util/error.c as well.
- Sahan
Samisa Abeysinghe wrote:
> BTW, to remind to all developers, the comment on top of an error code
> is supposed to be the error description used in the error-code/message
> mapping in the error.c file. When you update the missing values please
> keep this convention in mind, to help make error codes more
> understandable.
>
> Samisa...
>
> Samisa Abeysinghe wrote:
>
>> +1.
>> As far as you keep all the error codes in between AXIS2_ERROR_NONE
>> and AXIS2_ERROR_LAST, there would be minimal side effects.
>>
>> Also note that we need to open up some set of error codes to stub and
>> skeleton, so that user can let the engine know what went wrong in the
>> user code. Those should have some room in the hierarchy, even though
>> we are yet to define such errors codes.
>>
>> Thnaks,
>> Samisa...
>>
>> Sahan Gamage wrote:
>>
>>> Yah. Seems to be a good idea.
>>> So let's have a *common* category.
>>> - Sahan
>>> Nabeel wrote:
>>>
>>>
>>>
>>>> Sahan,
>>>> Are you going to introduce another group (e.g. name COMMON) to put
>>>> errors that do not specifically belong to any module listed in the
>>>> tree layout? You'll have to spend some time to figure out the common
>>>> ones to prevent duplication :)
>>>> some simple examples:
>>>> No Memory
>>>> Invalid Null Argument
>>>> Our of range value for an axis2 defined enum
>>>>
>>>> thanks
>>>> -Nabeel
>>>>
>>>> Sahan Gamage wrote:
>>>>
>>>>
>>>>
>>>>> Hi all,
>>>>>
>>>>> I am planning to reorganize the error codes in error.h as well as
>>>>> in the
>>>>> error.c. Following is the option that comes into my mind about the
>>>>> way I
>>>>> am going to organize the codes.
>>>>> The directory hierarchy of the modules directory of current axis2c
>>>>> implementation is as follows.
>>>>>
>>>>> modules
>>>>> |
>>>>> |-core
>>>>> | |-addr
>>>>> | |-clientapi
>>>>> | | |-diclient
>>>>> | |-context
>>>>> | |-deployment
>>>>> | |-description
>>>>> | |-engine
>>>>> | |-phaseresolver
>>>>> | |-receivers
>>>>> | |-transport
>>>>> | | |-http
>>>>> | | | |-receiver
>>>>> | | | |-sender
>>>>> | | | | |-ssl (will be there soon)
>>>>> | | | |-server
>>>>> | | | | |-apache2
>>>>> | | | | |-simple_axis2_server | |-util
>>>>> |-mod_addr
>>>>> |-platforms
>>>>> | |-unix
>>>>> | |-windows
>>>>> |-util
>>>>> |-wsdl
>>>>> |-xml
>>>>> | |-attachments
>>>>> | |-om
>>>>> | |-parser
>>>>> | | |-guththila
>>>>> | | |-libxml2
>>>>> | |-soap
>>>>>
>>>>> Note that I have specifically ignored woden and xml_schema since
>>>>> we are
>>>>> not finalized the status of these projects (eg: whether to
>>>>> separate them
>>>>> as new projects)
>>>>>
>>>>> So the order of the error codes will be the order we get by
>>>>> flattening
>>>>> the above hierarchy.
>>>>> Next is the convention of the error codes. I assume the convention
>>>>> proposed by samisa in AXIS2C-67.
>>>>> Also there are lot of error codes which doesn't have descriptions
>>>>> along
>>>>> with them. If the respective authors can update the error.h with the
>>>>> comments I can update the descriptions in the error.c file. Pls take
>>>>> some time to do that before the next release.
>>>>>
>>>>> Comments are welcome for the above proposal
>>>>>
>>>>> - Sahan
>>>>>
>>>>>
>>>>>
>>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
Re: [Axis2]Organizing the error codes
Posted by Samisa Abeysinghe <sa...@gmail.com>.
BTW, to remind to all developers, the comment on top of an error code is
supposed to be the error description used in the error-code/message
mapping in the error.c file. When you update the missing values please
keep this convention in mind, to help make error codes more understandable.
Samisa...
Samisa Abeysinghe wrote:
> +1.
> As far as you keep all the error codes in between AXIS2_ERROR_NONE and
> AXIS2_ERROR_LAST, there would be minimal side effects.
>
> Also note that we need to open up some set of error codes to stub and
> skeleton, so that user can let the engine know what went wrong in the
> user code. Those should have some room in the hierarchy, even though
> we are yet to define such errors codes.
>
> Thnaks,
> Samisa...
>
> Sahan Gamage wrote:
>
>> Yah. Seems to be a good idea.
>> So let's have a *common* category.
>> - Sahan
>> Nabeel wrote:
>>
>>
>>
>>> Sahan,
>>> Are you going to introduce another group (e.g. name COMMON) to put
>>> errors that do not specifically belong to any module listed in the
>>> tree layout? You'll have to spend some time to figure out the common
>>> ones to prevent duplication :)
>>> some simple examples:
>>> No Memory
>>> Invalid Null Argument
>>> Our of range value for an axis2 defined enum
>>>
>>> thanks
>>> -Nabeel
>>>
>>> Sahan Gamage wrote:
>>>
>>>
>>>
>>>> Hi all,
>>>>
>>>> I am planning to reorganize the error codes in error.h as well as
>>>> in the
>>>> error.c. Following is the option that comes into my mind about the
>>>> way I
>>>> am going to organize the codes.
>>>> The directory hierarchy of the modules directory of current axis2c
>>>> implementation is as follows.
>>>>
>>>> modules
>>>> |
>>>> |-core
>>>> | |-addr
>>>> | |-clientapi
>>>> | | |-diclient
>>>> | |-context
>>>> | |-deployment
>>>> | |-description
>>>> | |-engine
>>>> | |-phaseresolver
>>>> | |-receivers
>>>> | |-transport
>>>> | | |-http
>>>> | | | |-receiver
>>>> | | | |-sender
>>>> | | | | |-ssl (will be there soon)
>>>> | | | |-server
>>>> | | | | |-apache2
>>>> | | | | |-simple_axis2_server | |-util
>>>> |-mod_addr
>>>> |-platforms
>>>> | |-unix
>>>> | |-windows
>>>> |-util
>>>> |-wsdl
>>>> |-xml
>>>> | |-attachments
>>>> | |-om
>>>> | |-parser
>>>> | | |-guththila
>>>> | | |-libxml2
>>>> | |-soap
>>>>
>>>> Note that I have specifically ignored woden and xml_schema since we
>>>> are
>>>> not finalized the status of these projects (eg: whether to separate
>>>> them
>>>> as new projects)
>>>>
>>>> So the order of the error codes will be the order we get by flattening
>>>> the above hierarchy.
>>>> Next is the convention of the error codes. I assume the convention
>>>> proposed by samisa in AXIS2C-67.
>>>> Also there are lot of error codes which doesn't have descriptions
>>>> along
>>>> with them. If the respective authors can update the error.h with the
>>>> comments I can update the descriptions in the error.c file. Pls take
>>>> some time to do that before the next release.
>>>>
>>>> Comments are welcome for the above proposal
>>>>
>>>> - Sahan
>>>>
>>>>
>>>>
>>>>
>>>
>>>
>>
>>
>>
>>
>>
>
>
Re: [Axis2]Organizing the error codes
Posted by Samisa Abeysinghe <sa...@gmail.com>.
+1.
As far as you keep all the error codes in between AXIS2_ERROR_NONE and
AXIS2_ERROR_LAST, there would be minimal side effects.
Also note that we need to open up some set of error codes to stub and
skeleton, so that user can let the engine know what went wrong in the
user code. Those should have some room in the hierarchy, even though we
are yet to define such errors codes.
Thnaks,
Samisa...
Sahan Gamage wrote:
>Yah. Seems to be a good idea.
>So let's have a *common* category.
>- Sahan
>Nabeel wrote:
>
>
>
>>Sahan,
>>Are you going to introduce another group (e.g. name COMMON) to put
>>errors that do not specifically belong to any module listed in the
>>tree layout? You'll have to spend some time to figure out the common
>>ones to prevent duplication :)
>>some simple examples:
>>No Memory
>>Invalid Null Argument
>>Our of range value for an axis2 defined enum
>>
>>thanks
>>-Nabeel
>>
>>Sahan Gamage wrote:
>>
>>
>>
>>>Hi all,
>>>
>>>I am planning to reorganize the error codes in error.h as well as in the
>>>error.c. Following is the option that comes into my mind about the way I
>>>am going to organize the codes.
>>>The directory hierarchy of the modules directory of current axis2c
>>>implementation is as follows.
>>>
>>>modules
>>>|
>>>|-core
>>>| |-addr
>>>| |-clientapi
>>>| | |-diclient
>>>| |-context
>>>| |-deployment
>>>| |-description
>>>| |-engine
>>>| |-phaseresolver
>>>| |-receivers
>>>| |-transport
>>>| | |-http
>>>| | | |-receiver
>>>| | | |-sender
>>>| | | | |-ssl (will be there soon)
>>>| | | |-server
>>>| | | | |-apache2
>>>| | | | |-simple_axis2_server | |-util
>>>|-mod_addr
>>>|-platforms
>>>| |-unix
>>>| |-windows
>>>|-util
>>>|-wsdl
>>>|-xml
>>>| |-attachments
>>>| |-om
>>>| |-parser
>>>| | |-guththila
>>>| | |-libxml2
>>>| |-soap
>>>
>>>Note that I have specifically ignored woden and xml_schema since we are
>>>not finalized the status of these projects (eg: whether to separate them
>>>as new projects)
>>>
>>>So the order of the error codes will be the order we get by flattening
>>>the above hierarchy.
>>>Next is the convention of the error codes. I assume the convention
>>>proposed by samisa in AXIS2C-67.
>>>Also there are lot of error codes which doesn't have descriptions along
>>>with them. If the respective authors can update the error.h with the
>>>comments I can update the descriptions in the error.c file. Pls take
>>>some time to do that before the next release.
>>>
>>>Comments are welcome for the above proposal
>>>
>>>- Sahan
>>>
>>>
>>>
>>>
>>>
>>
>>
>
>
>
>
Re: [Axis2]Organizing the error codes
Posted by Sahan Gamage <sa...@wso2.com>.
Yah. Seems to be a good idea.
So let's have a *common* category.
- Sahan
Nabeel wrote:
> Sahan,
> Are you going to introduce another group (e.g. name COMMON) to put
> errors that do not specifically belong to any module listed in the
> tree layout? You'll have to spend some time to figure out the common
> ones to prevent duplication :)
> some simple examples:
> No Memory
> Invalid Null Argument
> Our of range value for an axis2 defined enum
>
> thanks
> -Nabeel
>
> Sahan Gamage wrote:
>
>> Hi all,
>>
>> I am planning to reorganize the error codes in error.h as well as in the
>> error.c. Following is the option that comes into my mind about the way I
>> am going to organize the codes.
>> The directory hierarchy of the modules directory of current axis2c
>> implementation is as follows.
>>
>> modules
>> |
>> |-core
>> | |-addr
>> | |-clientapi
>> | | |-diclient
>> | |-context
>> | |-deployment
>> | |-description
>> | |-engine
>> | |-phaseresolver
>> | |-receivers
>> | |-transport
>> | | |-http
>> | | | |-receiver
>> | | | |-sender
>> | | | | |-ssl (will be there soon)
>> | | | |-server
>> | | | | |-apache2
>> | | | | |-simple_axis2_server | |-util
>> |-mod_addr
>> |-platforms
>> | |-unix
>> | |-windows
>> |-util
>> |-wsdl
>> |-xml
>> | |-attachments
>> | |-om
>> | |-parser
>> | | |-guththila
>> | | |-libxml2
>> | |-soap
>>
>> Note that I have specifically ignored woden and xml_schema since we are
>> not finalized the status of these projects (eg: whether to separate them
>> as new projects)
>>
>> So the order of the error codes will be the order we get by flattening
>> the above hierarchy.
>> Next is the convention of the error codes. I assume the convention
>> proposed by samisa in AXIS2C-67.
>> Also there are lot of error codes which doesn't have descriptions along
>> with them. If the respective authors can update the error.h with the
>> comments I can update the descriptions in the error.c file. Pls take
>> some time to do that before the next release.
>>
>> Comments are welcome for the above proposal
>>
>> - Sahan
>>
>>
>>
>
>
Re: [Axis2]Organizing the error codes
Posted by Nabeel <na...@wso2.com>.
Sahan,
Are you going to introduce another group (e.g. name COMMON) to put
errors that do not specifically belong to any module listed in the tree
layout? You'll have to spend some time to figure out the common ones to
prevent duplication :)
some simple examples:
No Memory
Invalid Null Argument
Our of range value for an axis2 defined enum
thanks
-Nabeel
Sahan Gamage wrote:
>Hi all,
>
>I am planning to reorganize the error codes in error.h as well as in the
>error.c. Following is the option that comes into my mind about the way I
>am going to organize the codes.
>The directory hierarchy of the modules directory of current axis2c
>implementation is as follows.
>
>modules
>|
>|-core
>| |-addr
>| |-clientapi
>| | |-diclient
>| |-context
>| |-deployment
>| |-description
>| |-engine
>| |-phaseresolver
>| |-receivers
>| |-transport
>| | |-http
>| | | |-receiver
>| | | |-sender
>| | | | |-ssl (will be there soon)
>| | | |-server
>| | | | |-apache2
>| | | | |-simple_axis2_server
>| |-util
>|-mod_addr
>|-platforms
>| |-unix
>| |-windows
>|-util
>|-wsdl
>|-xml
>| |-attachments
>| |-om
>| |-parser
>| | |-guththila
>| | |-libxml2
>| |-soap
>
>Note that I have specifically ignored woden and xml_schema since we are
>not finalized the status of these projects (eg: whether to separate them
>as new projects)
>
>So the order of the error codes will be the order we get by flattening
>the above hierarchy.
>Next is the convention of the error codes. I assume the convention
>proposed by samisa in AXIS2C-67.
>Also there are lot of error codes which doesn't have descriptions along
>with them. If the respective authors can update the error.h with the
>comments I can update the descriptions in the error.c file. Pls take
>some time to do that before the next release.
>
>Comments are welcome for the above proposal
>
>- Sahan
>
>
>