[jira] Commented: (AXIS2C-976) base64 encode length returns size of encoded string + 1.

[ https://issues.apache.org/jira/browse/AXIS2C-976?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608306#action_12608306 ] Senaka Fernando commented on AXIS2C-976: Well this is not a question about backward

[jira] Commented: (AXIS2C-721) Requesting step-by-step guides

[ https://issues.apache.org/jira/browse/AXIS2C-721?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608307#action_12608307 ] Senaka Fernando commented on AXIS2C-721: Hi Supun, Yep this can be considered reso

[jira] Commented: (AXIS2C-1203) More readable LOG Macros.

[ https://issues.apache.org/jira/browse/AXIS2C-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608309#action_12608309 ] Damitha Kumarage commented on AXIS2C-1203: -- It seems to me that the patch has a s

[jira] Commented: (AXIS2C-1058) Most recent fixes to Simple Axis2 HTTP Server and mod_axis2 have not reflected in the IIS Module

[ https://issues.apache.org/jira/browse/AXIS2C-1058?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608308#action_12608308 ] Senaka Fernando commented on AXIS2C-1058: - Hi Supun, Thanks for the Fix. There wa

[jira] Commented: (AXIS2C-1001) Axis2/C Stress tests fail

[ https://issues.apache.org/jira/browse/AXIS2C-1001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608311#action_12608311 ] Senaka Fernando commented on AXIS2C-1001: - Hi Frank, Yes, I think the timeout int

[jira] Commented: (AXIS2C-1040) Use of AXIS2_EXPORT instead of AXIS2_EXTERN in a few places causes errors in static build

[ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608312#action_12608312 ] Senaka Fernando commented on AXIS2C-1040: - Hi Dushshantha, Well there was an inst

[jira] Commented: (AXIS2C-1180) SSL Communication and the CA certificate

[ https://issues.apache.org/jira/browse/AXIS2C-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608316#action_12608316 ] Senaka Fernando commented on AXIS2C-1180: - Hi Frank, The certificate from the ser

[jira] Commented: (AXIS2C-1192) axis2c dual sample clients give a memory corruption in consecutive execution

[ https://issues.apache.org/jira/browse/AXIS2C-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608318#action_12608318 ] Senaka Fernando commented on AXIS2C-1192: - Hi Shankar, Could this issue be relate

[jira] Resolved: (AXIS2C-1179) Axis2-C Unicode Support

[ https://issues.apache.org/jira/browse/AXIS2C-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva resolved AXIS2C-1179. - Resolution: Won't Fix Moving to Axis2/C 2.0. > Axis2-C Unicode Support > --

[jira] Assigned: (AXIS2C-1180) SSL Communication and the CA certificate

[ https://issues.apache.org/jira/browse/AXIS2C-1180?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando reassigned AXIS2C-1180: --- Assignee: Senaka Fernando > SSL Communication and the CA certificate > -

[jira] Commented: (AXIS2C-1201) When same operation is defined in Service level as well as module level, service level operation should be used.

[ https://issues.apache.org/jira/browse/AXIS2C-1201?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608322#action_12608322 ] Damitha Kumarage commented on AXIS2C-1201: -- Module is a way of extention to the A

[jira] Commented: (AXIS2C-1116) /WX (warn-to-error) flags in windows makefiles found in source distributions leads to build breaks on 64-bit windows

[ https://issues.apache.org/jira/browse/AXIS2C-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608321#action_12608321 ] Supun Kamburugamuva commented on AXIS2C-1116: - Hi Everyone, This issue is mar

[jira] Updated: (AXIS2C-1203) More readable LOG Macros.

[ https://issues.apache.org/jira/browse/AXIS2C-1203?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruwan Janapriya updated AXIS2C-1203: Attachment: readable_macro_correction.patch That is true, readable_macro_correction.patch

[jira] Commented: (AXIS2C-1116) /WX (warn-to-error) flags in windows makefiles found in source distributions leads to build breaks on 64-bit windows

[ https://issues.apache.org/jira/browse/AXIS2C-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608328#action_12608328 ] Senaka Fernando commented on AXIS2C-1116: - Hi Supun, This will not require a 64-b

[jira] Issue Comment Edited: (AXIS2C-1116) /WX (warn-to-error) flags in windows makefiles found in source distributions leads to build breaks on 64-bit windows

[ https://issues.apache.org/jira/browse/AXIS2C-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608328#action_12608328 ] senakafdo edited comment on AXIS2C-1116 at 6/26/08 1:08 AM:

Re: [jira] Issue Comment Edited: (AXIS2C-1116) /WX (warn-to-error) flags in windows makefiles found in source distributions leads to build breaks on 64-bit windows

Hi Senaka, We still creates a win32 bin/src. Supun. On Thu, Jun 26, 2008 at 1:38 PM, Senaka Fernando (JIRA) <[EMAIL PROTECTED]> wrote: > >[ > https://issues.apache.org/jira/browse/AXIS2C-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608328#act

[jira] Commented: (AXIS2C-1192) axis2c dual sample clients give a memory corruption in consecutive execution

[ https://issues.apache.org/jira/browse/AXIS2C-1192?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608333#action_12608333 ] S.Uthaiyashankar commented on AXIS2C-1192: -- Here, echo_blocking_dual.exe crashes.

[jira] Assigned: (AXIS2C-1151) memory leak in code generated by WSDL2C, soap_act not freed

[ https://issues.apache.org/jira/browse/AXIS2C-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milinda Lakmal Pathirage reassigned AXIS2C-1151: Assignee: Milinda Lakmal Pathirage > memory leak in code generated

[jira] Updated: (AXIS2C-1040) AXIS2/C Static Build Required

[ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-1040: Issue Type: Improvement (was: Bug) Summary: AXIS2/C Static Build Required (was: Us

[jira] Commented: (AXIS2C-1154) multiple Invalid read of size 4 for client In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608349#action_12608349 ] Supun Kamburugamuva commented on AXIS2C-1154: - Hi Frederic, I assume the trac

[jira] Commented: (AXIS2C-1154) multiple Invalid read of size 4 for client In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608356#action_12608356 ] Frederic Heem commented on AXIS2C-1154: --- Indeed, MALLOC and FREE needs to be modifie

[jira] Reopened: (AXIS2C-1160) axis2_svc_client_send_robust_with_op_qname doesn't return AXIS2_FAILURE when the server returns "HTTP/1.1 500 Internal Server Error"

[ https://issues.apache.org/jira/browse/AXIS2C-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Frederic Heem reopened AXIS2C-1160: --- The problem has been checked again, and still exists. Please use the notify_client.c which cont

[jira] Commented: (AXIS2C-1154) multiple Invalid read of size 4 for client In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608366#action_12608366 ] Supun Kamburugamuva commented on AXIS2C-1154: - But I can see that function is

[jira] Commented: (AXIS2C-1154) multiple Invalid read of size 4 for client In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608377#action_12608377 ] Frederic Heem commented on AXIS2C-1154: --- In the given trace, axutil_allocator_free_i

[jira] Created: (AXIS2C-1204) memory leak for In-Only message with no parameter

memory leak for In-Only message with no parameter - Key: AXIS2C-1204 URL: https://issues.apache.org/jira/browse/AXIS2C-1204 Project: Axis2-C Issue Type: Bug Components: core/receivers

[jira] Commented: (AXIS2C-1040) AXIS2/C Static Build Required

[ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608390#action_12608390 ] Dushshantha Chandradasa commented on AXIS2C-1040: - I tested the svn head w

[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608416#action_12608416 ] Damitha Kumarage commented on AXIS2C-723: - We can solve this problem as following.

AddIing new transport in Axis2/C

Hi, Please see proposed solution for jira AXIS2C-723. If every body ok with this I can implement this within few hours. thanks Damitha - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECT

[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608418#action_12608418 ] Senaka Fernando commented on AXIS2C-723: Hi Damitha, This is the point. Say the us

[jira] Assigned: (AXIS2C-1040) AXIS2/C Static Build Required

[ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando reassigned AXIS2C-1040: --- Assignee: Senaka Fernando (was: Dushshantha Chandradasa) > AXIS2/C Static Build Req

[jira] Commented: (AXIS2C-1040) AXIS2/C Static Build Required

[ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608420#action_12608420 ] Senaka Fernando commented on AXIS2C-1040: - Hi Dushshantha, Thanks for the confirm

[jira] Updated: (AXIS2C-1040) AXIS2/C Static Build Required

[ https://issues.apache.org/jira/browse/AXIS2C-1040?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-1040: Environment: MS Windows > AXIS2/C Static Build Required > - >

[jira] Commented: (AXIS2C-1160) axis2_svc_client_send_robust_with_op_qname doesn't return AXIS2_FAILURE when the server returns "HTTP/1.1 500 Internal Server Error"

[ https://issues.apache.org/jira/browse/AXIS2C-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608422#action_12608422 ] Senaka Fernando commented on AXIS2C-1160: - Hi Frederic, Can you provide us with i

[jira] Commented: (AXIS2C-1190) Non blocking samples could be improved by the use of axis2_callback_get_complete function.

[ https://issues.apache.org/jira/browse/AXIS2C-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608424#action_12608424 ] Senaka Fernando commented on AXIS2C-1190: - Hi Damitha, This is something related

[jira] Issue Comment Edited: (AXIS2C-1190) Non blocking samples could be improved by the use of axis2_callback_get_complete function.

[ https://issues.apache.org/jira/browse/AXIS2C-1190?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608424#action_12608424 ] senakafdo edited comment on AXIS2C-1190 at 6/26/08 6:37 AM:

[jira] Commented: (AXIS2C-1160) axis2_svc_client_send_robust_with_op_qname doesn't return AXIS2_FAILURE when the server returns "HTTP/1.1 500 Internal Server Error"

[ https://issues.apache.org/jira/browse/AXIS2C-1160?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608426#action_12608426 ] Frederic Heem commented on AXIS2C-1160: --- The modified notify_client.c has been used

[jira] Created: (AXIS2C-1205) Redundant adding of handlers into execution chains.

Redundant adding of handlers into execution chains. --- Key: AXIS2C-1205 URL: https://issues.apache.org/jira/browse/AXIS2C-1205 Project: Axis2-C Issue Type: Bug Environment: all

[jira] Resolved: (AXIS2C-1116) /WX (warn-to-error) flags in windows makefiles found in source distributions leads to build breaks on 64-bit windows

[ https://issues.apache.org/jira/browse/AXIS2C-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera resolved AXIS2C-1116. Resolution: Fixed > /WX (warn-to-error) flags in windows makefiles found in source

[jira] Assigned: (AXIS2C-1116) /WX (warn-to-error) flags in windows makefiles found in source distributions leads to build breaks on 64-bit windows

[ https://issues.apache.org/jira/browse/AXIS2C-1116?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sanjaya Ratnaweera reassigned AXIS2C-1116: -- Assignee: Sanjaya Ratnaweera (was: Senaka Fernando) > /WX (warn-to-error) fla

[jira] Created: (AXIS2C-1206) xsd:unsignedByte is tranlated to a char, which is signed

xsd:unsignedByte is tranlated to a char, which is signed Key: AXIS2C-1206 URL: https://issues.apache.org/jira/browse/AXIS2C-1206 Project: Axis2-C Issue Type: Bug Components:

[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608467#action_12608467 ] Damitha Kumarage commented on AXIS2C-723: - As I can see where existing transport li

[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608470#action_12608470 ] Senaka Fernando commented on AXIS2C-723: Hi Damitha, If you can avoid hardcoding t

[jira] Updated: (AXISCPP-458) Unwrapped not supported.

[ https://issues.apache.org/jira/browse/AXISCPP-458?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] nadir amra updated AXISCPP-458: --- Component/s: (was: WSDL processing - RPC) Fix Version/s: (was: 1.6 Alpha)

Refactoring the transport

Hi devs, Most of the code in Axis2/C transport is not organized properly. This makes it very difficult to do some changes or adding new functionality to the code. One main reason for this is REST handling and SOAP handling are mixed in the code in a very ugly manner. Axis2/JAVA has a separate sect

[jira] Commented: (AXISCPP-900) Attributes not settable for webservice incvocation

[ https://issues.apache.org/jira/browse/AXISCPP-900?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608490#action_12608490 ] nadir amra commented on AXISCPP-900: This will be fixed soon. Now that I understand w

Re: Refactoring the transport

Hi Manjula, Manjula Peiris wrote: Hi devs, Most of the code in Axis2/C transport is not organized properly. This makes it very difficult to do some changes or adding new functionality to the code. One main reason for this is REST handling and SOAP handling are mixed in the code in a very ugly ma

Re: Refactoring the transport

On Thu, 2008-06-26 at 23:57 +0530, Damitha Kumarage wrote: > Hi Manjula, > Manjula Peiris wrote: > > Hi devs, > > > > Most of the code in Axis2/C transport is not organized properly. This > > makes it very difficult to do some changes or adding new functionality > > to the code. One main reason fo

[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608645#action_12608645 ] Danushka Menikkumbura commented on AXIS2C-723: -- Hi Damitha, We already have t

Re: Refactoring the transport

Manjula Peiris wrote: Hi devs, Most of the code in Axis2/C transport is not organized properly. This makes it very difficult to do some changes or adding new functionality to the code. One main reason for this is REST handling and SOAP handling are mixed in the code in a very ugly manner. Axis2/

Re: Refactoring the transport

Hi all, +1 for refactoring the HTTP transport sections and +1 for having a good set of test cases. Since we are agreeing to doing this, I suggest we should have a good design before going on. I think we have enough knowledge and experience to get this right at this point. So I'm looking forward t

Re: Refactoring the transport

Supun Kamburugamuva wrote: Hi all, +1 for refactoring the HTTP transport sections and +1 for having a good set of test cases. Since we are agreeing to doing this, I suggest we should have a good design before going on. I think we have enough knowledge and experience to get this right at thi

[jira] Commented: (AXIS2C-1154) multiple Invalid read of size 4 for client In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608649#action_12608649 ] Supun Kamburugamuva commented on AXIS2C-1154: - Hi Fredric, I think you have a

Re: Refactoring the transport

On Fri, Jun 27, 2008 at 9:29 AM, Samisa Abeysinghe <[EMAIL PROTECTED]> wrote: > Supun Kamburugamuva wrote: > >> Hi all, >> >> +1 for refactoring the HTTP transport sections and +1 for having a good >> set of test cases. >> >> Since we are agreeing to doing this, I suggest we should have a good >>

Test suite for HTTP transport

Hi list, These are the key areas that comes to my mind that we should focus on for testing. 1. It should work for all sorts of HTTP scenarios. Headers and data are the key things. We can focus on different combinations. 2. Should not leak memory 3. Should have good performance characteristics Th

Re: Test suite for HTTP transport

Sorry I guess this is not the correct discussion for refactoring the transport. Supun.. On Fri, Jun 27, 2008 at 10:09 AM, Supun KamSoburugamuva <[EMAIL PROTECTED]> wrote: > Hi list, > > These are the key areas that comes to my mind that we should focus on for > testing. > > 1. It should work for

Re: Test suite for HTTP transport

Do you think this is the correct discussion for refactoring the transport? Or I'm I missing something? Supun.. On Fri, Jun 27, 2008 at 10:09 AM, Supun Kamburugamuva <[EMAIL PROTECTED]> wrote: > Hi list, > > These are the key areas that comes to my mind that we should focus on for > testing. > >

Re: Refactoring the transport

+1 for implementing tests first. Thanks Milinda... On Fri, Jun 27, 2008 at 9:58 AM, Rajika Kumarasiri <[EMAIL PROTECTED]> wrote: > > > On Fri, Jun 27, 2008 at 9:29 AM, Samisa Abeysinghe <[EMAIL PROTECTED]> > wrote: > >> Supun Kamburugamuva wrote: >> >>> Hi all, >>> >>> +1 for refactoring the HTT

Re: Refactoring the transport

Hi, I don't think we need to design new test suites at this time. What we need to do is adding comprehensive number of tests into the existing test suite sufficient for testing the focused code of refactoring. As I remember we worked on two test suites in the past but did not proceed adding mo

Re: Test suite for HTTP transport

Hi Supun, Actually what you have mentioned about HTTP transport is correct. But we have to consider other transports as well. I think you forgot them somehow ;-). I think what we have to test is the functionality of Axis2/C engine when it uses different transports. We have to make sure that Axis2/

Re: Refactoring the transport

On Fri, Jun 27, 2008 at 10:37 AM, Damitha Kumarage <[EMAIL PROTECTED]> wrote: > Hi, > I don't think we need to design new test suites at this time. What we need > to do is adding comprehensive number of tests into the existing test suite > sufficient for testing the focused code of refactoring. As

Test suite for transports [was: Re: Test suite for HTTP transport]

Supun Kamburugamuva wrote: Do you think this is the correct discussion for refactoring the transport? Or I'm I missing something? OK, I fixed the subject :) I think, in addition to what you have mentioned, the testing should also verify: 1. Content received and content sent 2. Transport sp

[jira] Commented: (AXIS2C-723) add new transport in Axis2/C

[ https://issues.apache.org/jira/browse/AXIS2C-723?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608663#action_12608663 ] Damitha Kumarage commented on AXIS2C-723: - I am thinking whether there is possiblit

[jira] Updated: (AXIS2C-1154) multiple Invalid read of size 4 for client In-Only message

[ https://issues.apache.org/jira/browse/AXIS2C-1154?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva updated AXIS2C-1154: Attachment: send_robust.patch Here is a fix for handling incorrect message pattern

[jira] Resolved: (AXIS2C-1151) memory leak in code generated by WSDL2C, soap_act not freed

[ https://issues.apache.org/jira/browse/AXIS2C-1151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Milinda Lakmal Pathirage resolved AXIS2C-1151. -- Resolution: Fixed Fix Version/s: Current (Nightly) Fix apply to

[jira] Commented: (AXIS2C-1204) memory leak for In-Only message with no parameter

[ https://issues.apache.org/jira/browse/AXIS2C-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12608670#action_12608670 ] Supun Kamburugamuva commented on AXIS2C-1204: - Hi Fredric, It is not clear to

[jira] Assigned: (AXIS2C-1204) memory leak for In-Only message with no parameter

[ https://issues.apache.org/jira/browse/AXIS2C-1204?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Supun Kamburugamuva reassigned AXIS2C-1204: --- Assignee: Supun Kamburugamuva > memory leak for In-Only message with no para