[AXIS2C ] Using a macro to convert between impl_t structs and interface structs

Hi All , By using a macro to convert between _impl_t struct and interface struct can make life easier in writing code since we can replace castings with macros. Eg To convert between axis2_om_node struct and axis2_om_node_impl_t struct we can use a macro AXIS2_INTF_TO_IMPL(node)

[jira] Commented: (AXISCPP-860) ComplexLists test is failing due to wrong request message

[ http://issues.apache.org/jira/browse/AXISCPP-860?page=comments#action_12356688 ] Dushshantha Chandradasa commented on AXISCPP-860: - I removed the modifications that i have introdused, so the test is working fine now. The response message

[jira] Commented: (AXISCPP-860) ComplexLists test is failing due to wrong request message

[ http://issues.apache.org/jira/browse/AXISCPP-860?page=comments#action_12356689 ] John Hawkins commented on AXISCPP-860: -- We should not be redeclaring the ns time and time again. This is really poor. Can you change it to be more intelligent?

[jira] Commented: (AXISCPP-860) ComplexLists test is failing due to wrong request message

[ http://issues.apache.org/jira/browse/AXISCPP-860?page=comments#action_12356693 ] Dushshantha Chandradasa commented on AXISCPP-860: - I'm trying to give a fix to question No.2. My first question should be 1. Why do we skip ns2 and

[AXIS2] Suggestion for change in coding convention

Hi all, For formating function signature , can we use the follwing formatting eg axis2_status_t AXIS2_CALL axis2_om_node_set_parent(axis2_om_node_t *om_node, axis2_env_t **env, axis2_om_node_t *parent); This will make the code look more consistent, pls comment in this .. regards ..

Re: [AXIS2] Suggestion for change in coding convention

nandika jayawardana wrote: Hi all, For formating function signature , can we use the follwing formatting eg axis2_status_t AXIS2_CALL axis2_om_node_set_parent(axis2_om_node_t *om_node, axis2_env_t **env,

[AXIS2] using a macro for parameter checking

Hi all, I think we can use a macro for parameter validation in the code, currently for all in parameters to functions we use if(!param) { (*env)-error-error_number = AXIS2_ERROR_INVALID_NULL_PARAMETER; return NULL; /* or appropriate return type */ } these lines are repeatedly used everywhere

Re: [AXIS2] using a macro for parameter checking

nandika jayawardana wrote: Hi all, I think we can use a macro for parameter validation in the code, cool currently for all in parameters to functions we use if(!param) { (*env)-error-error_number = AXIS2_ERROR_INVALID_NULL_PARAMETER; BTW you also need to set the status code

Re: [AXIS2] using a macro for parameter checking

nandika jayawardana wrote: Hi all, I think we can use a macro for parameter validation in the code, currently for all in parameters to functions we use if(!param) { (*env)-error-error_number = AXIS2_ERROR_INVALID_NULL_PARAMETER; return NULL; /* or appropriate return type */ } these

Re: [AXIS2] Suggestion for change in coding convention

Damitha Kumarage wrote: nandika jayawardana wrote: Hi all, For formating function signature , can we use the follwing formatting eg axis2_status_t AXIS2_CALL axis2_om_node_set_parent(axis2_om_node_t *om_node, axis2_env_t **env,

Some of the tests are Client Compilation - FAILED

Hi guys, Today following tests are Client Compilation fails with this error. E.g. XSD_NMTOKEN [cc] XSD_NMTOKENPort.cpp [cc] C:\obj\test\generated\cpp\XSD_NMTOKEN\XSD_NMTOKENPort.cpp(164) : error C2440: '=' : cannot convert from 'char ** ' to 'char *' [cc] Types pointed to are

[jira] Commented: (AXISCPP-834) ~xsd__hexBinary() needs to delete the contents of __ptr

[ http://issues.apache.org/jira/browse/AXISCPP-834?page=comments#action_12356753 ] Dushshantha Chandradasa commented on AXISCPP-834: - with following changes to ~xsd__hexBinary() xsd__hexBinary::~xsd__hexBinary() { if ( __ptr )