Name collision when using axutil_dir_windows.h

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

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

[ 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

[jira] Assigned: (AXIS2C-1101) Removed the AXIS2_ENV_CHECK and formated the asymmetric_binding.c in Neethi

[ https://issues.apache.org/jira/browse/AXIS2C-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera reassigned AXIS2C-1101: -- Assignee: Sanjaya Ratnaweera Removed the AXIS2_ENV_CHECK and formated the

[jira] Assigned: (AXIS2C-1100) Removed all the unnecessary AXIS2_ENV_CHECK from algorithmsuite.c in Neethi

[ https://issues.apache.org/jira/browse/AXIS2C-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera reassigned AXIS2C-1100: -- Assignee: Sanjaya Ratnaweera Removed all the unnecessary AXIS2_ENV_CHECK

[jira] Resolved: (AXIS2C-1101) Removed the AXIS2_ENV_CHECK and formated the asymmetric_binding.c in Neethi

[ https://issues.apache.org/jira/browse/AXIS2C-1101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-1101. Resolution: Fixed Fix Version/s: 1.3.1 Patch applied, thanks Manoj for the

[jira] Resolved: (AXIS2C-1100) Removed all the unnecessary AXIS2_ENV_CHECK from algorithmsuite.c in Neethi

[ https://issues.apache.org/jira/browse/AXIS2C-1100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-1100. Resolution: Fixed Fix Version/s: 1.3.1 Patch applied, thanks Manoj for the

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

[ https://issues.apache.org/jira/browse/AXIS2C-1103?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-1103. Resolution: Fixed Fix Version/s: 1.3.1 Patch applied, thanks Manoj for the

Re: Name collision when using axutil_dir_windows.h

If we add AXIS2_ or axis2_ prefix to the problem names, that should fix the stuff. Thanks, Samisa... Danushka Menikkumbura wrote: 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

Re: hello client in manual broken was [Re: I don't understand what is going on with memory control in a client.]

Hi Alex... I've gone through the manul and hello service and client works fine. Here's the request and response I recieved soapenv:Envelope xmlns:soapenv=http://www.w3.org/2003/05/soap-envelope; soapenv:Header/soapenv:Header soapenv:Body greetHello Server!/greet

[jira] Updated: (AXIS2C-1104) Name collision when using axutil_dir_windows.h

[ https://issues.apache.org/jira/browse/AXIS2C-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Danushka Menikkumbura updated AXIS2C-1104: -- Attachment: AXIS2C-1104.patch Please find the attached patch to fix the

[jira] Commented: (AXIS2C-1104) Name collision when using axutil_dir_windows.h

[ https://issues.apache.org/jira/browse/AXIS2C-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586752#action_12586752 ] Danushka Menikkumbura commented on AXIS2C-1104: --- Please note that I prefixed

Re: hello client in manual broken was [Re: I don't understand what is going on with memory control in a client.]

Hi again..., I just look at the subject of the mail and test whether hello client works or not. But that is not the issue and I tested the real issue and that's true. Client crashes when the response is not recieve (As an example after running the client without starting the server). I will fix

[jira] Resolved: (AXIS2C-1089) Hello Client in manual Broken

[ https://issues.apache.org/jira/browse/AXIS2C-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Lahiru Gunathilake resolved AXIS2C-1089. Resolution: Fixed Hello Client in manual Broken -

[jira] Issue Comment Edited: (AXIS2C-1089) Hello Client in manual Broken

[ https://issues.apache.org/jira/browse/AXIS2C-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586737#action_12586737 ] lahiru edited comment on AXIS2C-1089 at 4/8/08 3:47 AM:

[jira] Created: (AXIS2C-1104) Name collision when using axutil_dir_windows.h

Name collision when using axutil_dir_windows.h Key: AXIS2C-1104 URL: https://issues.apache.org/jira/browse/AXIS2C-1104 Project: Axis2-C Issue Type: Bug Components: util Affects

[jira] Resolved: (AXIS2C-915) Axis2/C licensing issue with it's dependencies

[ https://issues.apache.org/jira/browse/AXIS2C-915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-915. Resolution: Fixed Axis2/C licensing issue with it's dependencies

[jira] Commented: (AXIS2C-1089) Hello Client in manual Broken

[ https://issues.apache.org/jira/browse/AXIS2C-1089?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586737#action_12586737 ] Lahiru Gunathilake commented on AXIS2C-1089: hello client and service works

[jira] Resolved: (AXIS2C-1104) Name collision when using axutil_dir_windows.h

[ https://issues.apache.org/jira/browse/AXIS2C-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] S.Uthaiyashankar resolved AXIS2C-1104. -- Resolution: Fixed Fix Version/s: 1.3.1 Assignee: S.Uthaiyashankar

[jira] Commented: (AXIS2C-1104) Name collision when using axutil_dir_windows.h

[ https://issues.apache.org/jira/browse/AXIS2C-1104?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586774#action_12586774 ] S.Uthaiyashankar commented on AXIS2C-1104: -- Patch applyed. Thanks Danushka for

[jira] Commented: (AXIS2C-595) XPath support in AXIOM

[ https://issues.apache.org/jira/browse/AXIS2C-595?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12586778#action_12586778 ] Dinesh Premalal commented on AXIS2C-595: We have gsoc-2008 project related to

[jira] Assigned: (AXIS2C-1086) In function axis2_op_register_op_ctx() failure is logged and returned in a working path.

[ https://issues.apache.org/jira/browse/AXIS2C-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal reassigned AXIS2C-1086: --- Assignee: Dinesh Premalal In function axis2_op_register_op_ctx() failure is logged

[jira] Resolved: (AXIS2C-1086) In function axis2_op_register_op_ctx() failure is logged and returned in a working path.

[ https://issues.apache.org/jira/browse/AXIS2C-1086?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Dinesh Premalal resolved AXIS2C-1086. - Resolution: Fixed Fix Version/s: 1.3.1 This was happened because of the

Re: Regarding Axis2C architecture

Baxi, Rinilkumar (TCS) wrote: 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

Dual client reporing an error !!!

Hi all, I looked into the Jira (1005), and it seems to me that, in dual client scenario the response the client receives from the initial service (not from the replied service) does not contain an envelope, instead it just replies with setting the status code 202 (accepted). So that's why

[Axis2]Apache Axis2/C 1.3.1 RC1

Hi All, I packed and uploaded Apache Axis2/C 1.3.1 RC1 here [1]. Please test and send your feedback. thanks, Dinesh 1. http://people.apache.org/~dinesh/release/Axis2C-1.3.1-RC1/ -- http://nethu.org - To unsubscribe,