[jira] Resolved: (AXIS2C-1003) Memory leak in WSDL2C client code

2008-04-07 Thread Lahiru Gunathilake (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1003?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AXIS2C-1003. Resolution: Fixed > Memory leak in WSDL2C client code > --

Name collision when using "axutil_dir_windows.h"

2008-04-07 Thread Danushka Menikkumbura
This happened when I was trying to write an extension to PERL with the aid of SWIG. I came across two issues as mentioned below. 1. The struct name DIR declared in axutil_dir_windows.h collides with the DIR struct declared in dirent.h that comes with the standard PERL installation. 2. I get

Re: [Axis2][Vote]Dinesh as Release Manager

2008-04-07 Thread Samisa Abeysinghe
+1. Samisa... Damitha Kumarage wrote: Hi devs, I would like to propose Dinesh Premalal as the release manager for Apache Axis2/C 1.3.1 release. Since he has already volunteered to do so I would like to call a vote here to confirm his role as RM. Since we have identified few problems, it is

[jira] Updated: (AXIS2C-1103) Formated the code and added the relevant logs for binding_commons.c file

2008-04-07 Thread Manoj Pushpakumara (JIRA)
[ https://issues.apache.org/jira/browse/AXIS2C-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Manoj Pushpakumara updated AXIS2C-1103: --- Attachment: binding_commons.diff > Formated the code and added the relevant logs for

[jira] Created: (AXIS2C-1103) Formated the code and added the relevant logs for binding_commons.c file

2008-04-07 Thread Manoj Pushpakumara (JIRA)
Formated the code and added the relevant logs for binding_commons.c file - Key: AXIS2C-1103 URL: https://issues.apache.org/jira/browse/AXIS2C-1103 Project: Axis2-C Issu

Regarding Axis2C architecture

2008-04-07 Thread Baxi, Rinilkumar (TCS)
Hi All, Currently I am working on the design to invoke a legacy service through axis2c, which accepts character buffer as input and giving output is also in character buffer form. But as per my understanding on the existing Axis2c architecture is the last handler is the "Message Receiver" and