Re: [VOTE][AXIS2]Apache Axis2/C 1.6.0 Release artificats - Take2

+1. Thanks, Senaka On Mon, 2009-04-20 at 10:37 +0530, Dimuthu Gamage wrote: I tested the windows binary and all the samples were working fine. Here is my +1 for the release. Thanks Dimuthu On Mon, Apr 20, 2009 at 10:16 AM, Sanjaya Ratnaweera sanj...@wso2.com wrote: I tested

[jira] Commented: (AXIS2C-1312) axis2_http_client_connect_ssl_host() cannot make an https connection through http proxy when the proxy requires authentication

[ https://issues.apache.org/jira/browse/AXIS2C-1312?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12698348#action_12698348 ] Senaka Fernando commented on AXIS2C-1312: - Hi Dmitry, I'm trying to understand

[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-tabpanelfocusedCommentId=12608985#action_12608985 ] Senaka Fernando commented on AXIS2C-723: Hi Danushka, Damitha, If this can

[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-tabpanelfocusedCommentId=12608875#action_12608875 ] Senaka Fernando commented on AXIS2C-723: Hi Danushka, Damitha, Take this scenario

[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-tabpanelfocusedCommentId=12608308#action_12608308 ] Senaka Fernando commented on AXIS2C-1058: - Hi Supun, Thanks for the Fix

[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-tabpanelfocusedCommentId=12608311#action_12608311 ] Senaka Fernando commented on AXIS2C-1001: - Hi Frank, Yes, I think the timeout

[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-tabpanelfocusedCommentId=12608312#action_12608312 ] Senaka Fernando commented on AXIS2C-1040: - Hi Dushshantha, Well

[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-tabpanelfocusedCommentId=12608316#action_12608316 ] Senaka Fernando commented on AXIS2C-1180: - Hi Frank, The certificate from

[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-tabpanelfocusedCommentId=12608318#action_12608318 ] Senaka Fernando commented on AXIS2C-1192: - Hi Shankar, Could this issue

[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-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-tabpanelfocusedCommentId=12608328#action_12608328 ] Senaka Fernando commented on AXIS2C-1116: - Hi Supun, This will not require a 64

[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

we official have 64-bit support? or will still create the 32-bit src/bin releases? Regards, Senaka was (Author: senakafdo): Hi Supun, This will not require a 64-bit machine to fix, but will need a 64-bit machine to reproduce. What should be happening is that when we create

[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

[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

[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-tabpanelfocusedCommentId=12608420#action_12608420 ] Senaka Fernando commented on AXIS2C-1040: - Hi Dushshantha, Thanks

[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-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-tabpanelfocusedCommentId=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.

on-complete handle 2. The get_complete function will introduce a blocking nature to the non-blocking code paths. I say so because I believe that a non-blocking execution should be based on response events rather than response states. Regards, Senaka was (Author: senakafdo): Hi Damitha

[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-tabpanelfocusedCommentId=12608470#action_12608470 ] Senaka Fernando commented on AXIS2C-723: Hi Damitha, If you can avoid hardcoding

[jira] Commented: (AXIS2C-1187) HTTP Authentication related code should be moved to a separate method.

[ https://issues.apache.org/jira/browse/AXIS2C-1187?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604606#action_12604606 ] Senaka Fernando commented on AXIS2C-1187: - Hi Nandika, +1 Regards, Senaka HTTP

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

[ https://issues.apache.org/jira/browse/AXIS2C-1179?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12604608#action_12604608 ] Senaka Fernando commented on AXIS2C-1179: - Hi Dayakar, Where do you expect

Re: [jira] Created: (AXIS2C-1142) Circular dependency between engine and http_common libraries

Hi devs, AFAIK, this is because of the REST portions of the engine depending on the HTTP libraries. So if someone is not interested in REST can we instead not link these libraries? Regards, Senaka Circular dependency between engine and http_common libraries

Re: [jira] Created: (AXIS2C-1142) Circular dependency between engine and http_common libraries

? Thoughts? Regards, Senaka Hi Senaka, Did you mean something like providing a compile time flag for not including these stuff if rest is not needed? If that is the case we are in the same position when rest is needed (we have circular dependencies). Regards, Supun. On Thu, May 15, 2008 at 5:30

Re: [jira] Created: (AXIS2C-1142) Circular dependency between engine and http_common libraries

Hi again, I noticed that Steve came up with a patch, let me check on that first. It might be a better solution. Regards, Senaka Hi Supun, Yes, That needs to be sorted for the REST case. But, I believe that this rather a bug in the REST portion of the engine, and the SOAP portion should

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

://issues.apache.org/jira/browse/AXIS2C-1116 Project: Axis2-C Issue Type: Bug Components: build system (Windows) Affects Versions: 1.3.1 Environment: Windows-64bit, Axis2/C 1.3.1 source distributions Reporter: Senaka Fernando

Re: [Axis2]Apache Axis2/C 1.3.1 RC2

Hi all, I ran Axis2/C with the IIS module (WinXP + IIS 5.1). All samples ran well and no build issues etc. Regards, Senaka Hi all, There was a bug in guththila_un_init function and guththila_reader_free function which will cause memory leaks. Should I commit the fix into the trunk. I think

[jira] Commented: (AXIS2C-1079) sandesha2c dual channel samples are not working with apache2

[ https://issues.apache.org/jira/browse/AXIS2C-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590187#action_12590187 ] Senaka Fernando commented on AXIS2C-1079: - Hi Damitha, I think I fixed this issue

[jira] Commented: (AXIS2C-1110) Support debug and release versions

[ https://issues.apache.org/jira/browse/AXIS2C-1110?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590190#action_12590190 ] Senaka Fernando commented on AXIS2C-1110: - Hi Pim, I see your intention. OK

[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-tabpanelfocusedCommentId=12590191#action_12590191 ] Senaka Fernando commented on AXIS2C-723: Hi devs, Shall we have this done

[jira] Commented: (AXIS2C-252) Use __attribute__ ((warn_unused_result)) to detect failure to check function return values

[ https://issues.apache.org/jira/browse/AXIS2C-252?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12590193#action_12590193 ] Senaka Fernando commented on AXIS2C-252: Hi all, We do have all the necessary

Re: MSVCR80

Hi Devs, has anyone run Axis2/C win32 binary lately? If so, have you run into this issue. Regards, Senaka Hi Supun, Senaka Given the suggestions of Supun, I have tried the following without result: - removed the directory and unzipped the contents of axis2c-bin-1.3.0-win32.zip

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

+1, Regards, Senaka +1 Thanks Milinda On Thu, Apr 3, 2008 at 9:59 PM, Dimuthu Gamage [EMAIL PROTECTED] wrote: +1 Thanks Dimuthu On Thu, Apr 3, 2008 at 8:59 PM, Dumindu Pallewela [EMAIL PROTECTED] wrote: +1 Dumindu. On Thu, Apr 3, 2008 at 8:54 PM, Sanjaya Ratnaweera

Re: [Axis2]Making Guththila Default Parser

Hi all, I have been running Guththila all these days and never ran into issues. Regards, Senaka Dinesh Premalal wrote: Hi All, As we discussed earlier, I think better to make guththila default parser for Axis2/C. +1. Samisa

[jira] Assigned: (AXIS2C-1085) echo_blocking_auth sample send two messages and first one always fail

[ https://issues.apache.org/jira/browse/AXIS2C-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando reassigned AXIS2C-1085: --- Assignee: Senaka Fernando echo_blocking_auth sample send two messages and first

[jira] Commented: (AXIS2C-1085) echo_blocking_auth sample send two messages and first one always fail

[ https://issues.apache.org/jira/browse/AXIS2C-1085?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12582155#action_12582155 ] Senaka Fernando commented on AXIS2C-1085: - Damitha, I don't think that request

[jira] Commented: (AXIS2C-1079) sandesha2c dual channel samples are not working with apache2

[ https://issues.apache.org/jira/browse/AXIS2C-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581634#action_12581634 ] Senaka Fernando commented on AXIS2C-1079: - Hi Damitha, I just started looking

Revision 639197's Fixes violate RFC 2616

Hi all, It seems that Revision 639197 has replaced Axis2C/1.3.0 with Axis2/C 1.3.0 which is a violation of Product Tokens specification in RFC 2616. I recently corrected this, but, it seems that it has got back to what it was. :(... I apologize for the missing comment. Regards, Senaka

Revision 640355's Fixes violate RFC 2616 [was Revision 639197's Fixes violate RFC 2616]

Hi again, The revision should be corrected as, 640355. Sorry for the confusion. Regards, Senaka Hi all, It seems that Revision 639197 has replaced Axis2C/1.3.0 with Axis2/C 1.3.0 which is a violation of Product Tokens specification in RFC 2616. I recently corrected this, but, it seems

[jira] Commented: (AXIS2C-1079) sandesha2c dual channel samples are not working with apache2

[ https://issues.apache.org/jira/browse/AXIS2C-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581663#action_12581663 ] Senaka Fernando commented on AXIS2C-1079: - Hi Damitha, rm_echo_1_0

[jira] Commented: (AXIS2C-1079) sandesha2c dual channel samples are not working with apache2

[ https://issues.apache.org/jira/browse/AXIS2C-1079?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12581358#action_12581358 ] Senaka Fernando commented on AXIS2C-1079: - Hi Damitha, There is another issue

Re: Google Summer of Code - Implementation of the XPath specification in Axis/C

, Senaka Regards, Dumindu. -- Dumindu Pallewela http://blog.dumindu.com GPG ID: 0x9E131672 WSO2 | Oxygenating the Web Service Platform | http://wso2.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional

[jira] Resolved: (AXIS2C-1078) a new macro AXIS2_HANDLE_ERROR() combining AXIS2_ERROR_SET() and AXIS2_LOG_ERROR

[ https://issues.apache.org/jira/browse/AXIS2C-1078?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1078. - Resolution: Fixed Fixed Issue a new macro AXIS2_HANDLE_ERROR() combining

[jira] Resolved: (AXIS2C-618) Engine has a dependancy on HTTP transport.

[ https://issues.apache.org/jira/browse/AXIS2C-618?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-618. Resolution: Fixed Fix Version/s: Current (Nightly) Fixed Issue Engine has

Ability to Add New Transports to Axis2/C

] https://issues.apache.org/jira/browse/AXIS2C-723 Regards, Senaka - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: Google Summer of Code - Implementation of the XPath specification in Axis/C

, which has somewhat deferred due to C not being an OO Langauge. But, you are strongly adviced to follow the Apache AXIOM implementation as much as possible. I believe that [1] should be really useful in this concern. [1] http://ws.apache.org/commons/axiom/apidocs/index.html Regards, Senaka Hi

[jira] Created: (AXIS2C-1075) TCPMon C Tool Unusable with non-Local Hosts

Versions: Current (Nightly) Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: Current (Nightly) TCPMon C Tool is Unusable with non-Local Hosts. I recently tried, -th en.wikipedia.org with -tp 80, and I basically kept on getting 404 Errors. It seems

Axis2/C Hackathon: Correcting a mistake

FYI: Moving discussion to Axis2/C list. Read the inline reply Manjula Peiris wrote: On Wed, 2008-03-19 at 15:19 +0530, Senaka Fernando wrote: Hi all, We have a habit of lavishly using, AXIS2_ERROR_SET(env-error, AXIS2_ERROR_NO_MEMORY, AXIS2_FAILURE); However, we have to set this error only

Re: Error logs for AXIS2_ERROR_SET

Senaka Fernando wrote: Hi all, How about AXIS2_ERROR_SET_AND_LOG(env-error, ...) a new macro which combines the AXIS2_ERROR_SET() and AXIS2_LOG_ERROR(). What if we wanted to do more with this macro in the future? e.g. AXIS2_ERROR_SET_AND_LOG_AND_FOO_AND_BAR(env-error, ...) ? So why

[jira] Created: (AXIS2C-1078) a new macro AXIS2_HANDLE_ERROR() combining AXIS2_ERROR_SET() and AXIS2_LOG_ERROR

Issue Type: Improvement Components: util Affects Versions: Current (Nightly) Reporter: Senaka Fernando Assignee: Senaka Fernando Priority: Minor Fix For: Current (Nightly) A new macro AXIS2_HANDLE_ERROR() combining

[Fwd: Re: Axis2/C, C++ and 'undefined symbol: __gxx_personality_v0']

Original Message Subject: Re: Axis2/C, C++ and 'undefined symbol: __gxx_personality_v0' From:Senaka Fernando [EMAIL PROTECTED] Date:Thu, March 20, 2008 1:04 am To: [EMAIL PROTECTED

[jira] Resolved: (AXIS2C-1060) Support on Axis2/C Server Side to read Accept-Language and set Content-Language

[ https://issues.apache.org/jira/browse/AXIS2C-1060?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1060. - Resolution: Fixed Fixed Issue Support on Axis2/C Server Side to read Accept-Language

[jira] Resolved: (AXIS2C-1068) Formated the code and removed AXIS2_ENV_CHECK from stack.c file

[ https://issues.apache.org/jira/browse/AXIS2C-1068?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1068. - Resolution: Fixed Fix Version/s: Current (Nightly) Assignee: Senaka

[jira] Resolved: (AXIS2C-1066) Formated the code and removed AXIS2_ENV_CHECK from property.c file

[ https://issues.apache.org/jira/browse/AXIS2C-1066?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1066. - Resolution: Fixed Fix Version/s: Current (Nightly) Assignee: Senaka

[jira] Resolved: (AXIS2C-1069) Formated the code and added relevant logs in stream.c file

[ https://issues.apache.org/jira/browse/AXIS2C-1069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1069. - Resolution: Fixed Fix Version/s: Current (Nightly) Assignee: Senaka

[jira] Resolved: (AXIS2C-1070) Updated the cording conventions in string_util.c file

[ https://issues.apache.org/jira/browse/AXIS2C-1070?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1070. - Resolution: Fixed Fix Version/s: Current (Nightly) Assignee: Senaka

Re: [jira] Created: (AXIS2C-1067) Formated the code and added relevant logs to qname.c file

Hi Manoj, I think you forgot the attachment. Regards, Senaka Formated the code and added relevant logs to qname.c file - Key: AXIS2C-1067 URL: https://issues.apache.org/jira/browse/AXIS2C-1067

[jira] Resolved: (AXIS2C-1063) modified the md5.c file

[ https://issues.apache.org/jira/browse/AXIS2C-1063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1063. - Resolution: Fixed Fix Version/s: Current (Nightly) Assignee: Senaka

[jira] Resolved: (AXIS2C-1061) Ability for Simple Axis2 HTTP Server to specify Date and Server headers

[ https://issues.apache.org/jira/browse/AXIS2C-1061?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1061. - Resolution: Fixed Fixed Issue Ability for Simple Axis2 HTTP Server to specify Date

Re: Caching support for large attachments

parsing is still a better choice. To implement such, we will have to modify our mime_parser.c, and probably the data_handler implementation. Or if not, am I misunderstanding $subject? [1] http://www.w3.org/Protocols/rfc2616/rfc2616-sec13.html Regards, Senaka Senaka Fernando wrote: Hi Manjula

Re: Caching support for large attachments

Senaka Fernando wrote: Hi Samisa, IIRC, this discussion is on handling attachments and thus, does not relate to caching. Though $subject says Caching what actually was discussed was a mechanism to buffer the attachment in a file, rather than in memory, and that buffer has nothing to do

[jira] Created: (AXIS2C-1059) A 406 Error must be sent to the client, if the expected Content-Type or Charset-Encoding wasn't what was generated.

://issues.apache.org/jira/browse/AXIS2C-1059 Project: Axis2-C Issue Type: Improvement Components: transport/http Affects Versions: Current (Nightly) Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: Current (Nightly

Re: Caching support for large attachments

. That means read the attachment for the stream only when needed. Similar in concept to StAX parsing of XML. That will cause the stream to exhaust for the lifetime of the request isn't it? If not can you explain the procedure? Regards, Senaka This is because many small attachments == one big attachment

[jira] Commented: (AXIS2C-1059) A 406 Error must be sent to the client, if the expected Content-Type or Charset-Encoding wasn't what was generated.

[ https://issues.apache.org/jira/browse/AXIS2C-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579240#action_12579240 ] Senaka Fernando commented on AXIS2C-1059: - Fixed Issue in Simple Axis2 HTTP Server

[jira] Resolved: (AXIS2C-1059) A 406 Error must be sent to the client, if the expected Content-Type or Charset-Encoding wasn't what was generated.

[ https://issues.apache.org/jira/browse/AXIS2C-1059?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1059. - Resolution: Fixed Fixed Issue A 406 Error must be sent to the client, if the expected

[jira] Created: (AXIS2C-1060) Support on Axis2/C Server Side to read Accept-Language and set Content-Language

Issue Type: New Feature Components: transport/http Affects Versions: Current (Nightly) Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: Current (Nightly) Support on Axis2/C Server Side to read Accept-Language and set Content

[jira] Created: (AXIS2C-1061) Ability for Simple Axis2 HTTP Server to specify Date and Server headers

Type: Improvement Components: transport/http Affects Versions: Current (Nightly) Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: Current (Nightly) Ability for Simple Axis2 HTTP Server to specify Date and Server headers. The Apache

Re: Caching support for large attachments

.. Simply increase the socket time out in the client. +1, That sounds a good idea. Regards, Senaka -- Thilina Gunarathne - http://thilinag.blogspot.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e

Re: FW: Problem with Service deployed

, this is pretty confusing. +1 for some fixes in this concern. Regards, Senaka Infact there is a sample for the Calculator with codegen support inside the samples/codegen directory, Hope that set of samples are usefull for you Thanks Dimuthu On Fri, Mar 14, 2008 at 9:20 PM, Senaka Fernando [EMAIL

Re: Caching support for large attachments

in Axis2/C. Regards, Senaka thanks, Thilina Samisa... Regards, Senaka Hi, In Axis2/Java case we do write the attachment content directly from the InputStream to the File when the attachment size is larger than the threshold. This avoids loading

Re: Caching support for large attachments

implemented Session in Axis2/C. Regards, Senaka thanks, Thilina Samisa... Regards, Senaka Hi, In Axis2/Java case we do write the attachment content directly from the InputStream to the File when the attachment size is larger than the threshold

Re: FW: Problem with Service deployed

, we'll have to make those WSDLs found in the test/resources directory suitable for a Axis2/C context. We'll have to change the endpoints, namespaces etc. where ever it makes sense to do so. Regards, Senaka Hi Senaka, The wsdl in the samples/codegen is from the axis2/c test resources. I think

Preventing DOS attacks made to the Axis2/C server.

be reporting a 503 status. The information on number of concurrent requests that can be handled should probably go into the services.xml as it being a service specific number. A global defualt setting can possibly be stored in the axis2.xml. Thoughts? Regards, Senaka

Re: Caching support for large attachments

Hi Manjula, Please read my reply inline. Hi Senaka, I am confused here. I think you are taking the discussion to the beginning. Because in the receiving side we read till the end of the stream. Please see my first mail. No I'm not taking the discussion to the starting point. I'm rather

Re: Caching support for large attachments

the Mid Point of the buffer to the end. Then you will search again. You will iterate this procedure until you read less than half the size of the buffer. HTH, Regards, Senaka On Sat, 2008-03-15 at 16:03 +0530, Senaka Fernando wrote: Hi Manjula, Please read my reply inline. Hi Senaka, I am

Re: Caching support for large attachments

, Senaka HTH, Regards, Senaka On Sat, 2008-03-15 at 16:03 +0530, Senaka Fernando wrote: Hi Manjula, Please read my reply inline. Hi Senaka, I am confused here. I think you are taking the discussion to the beginning. Because in the receiving side we read till the end of the stream

[jira] Resolved: (AXIS2C-1054) HTTP Status 404 returned instead of 405, when doing REST calls

[ https://issues.apache.org/jira/browse/AXIS2C-1054?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1054. - Resolution: Fixed Fixed Issue HTTP Status 404 returned instead of 405, when doing

[jira] Created: (AXIS2C-1056) For a request with an un-supported HTTP Method Axis2/C server side replies with 202 Accepted, instead of 501 Not Implemented

URL: https://issues.apache.org/jira/browse/AXIS2C-1056 Project: Axis2-C Issue Type: Bug Components: transport/http Affects Versions: Current (Nightly) Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: Current

[jira] Commented: (AXIS2C-1056) For a request with an un-supported HTTP Method Axis2/C server side replies with 202 Accepted, instead of 501 Not Implemented

[ https://issues.apache.org/jira/browse/AXIS2C-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579080#action_12579080 ] Senaka Fernando commented on AXIS2C-1056: - A classical SOAP Engine would reply

[jira] Commented: (AXIS2C-1056) For a request with an un-supported HTTP Method Axis2/C server side replies with 202 Accepted, instead of 501 Not Implemented

[ https://issues.apache.org/jira/browse/AXIS2C-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12579083#action_12579083 ] Senaka Fernando commented on AXIS2C-1056: - It seems that mod_axis2 replies

[jira] Resolved: (AXIS2C-1056) For a request with an un-supported HTTP Method Axis2/C server side replies with 202 Accepted, instead of 501 Not Implemented

[ https://issues.apache.org/jira/browse/AXIS2C-1056?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1056. - Resolution: Fixed Fixed Issue For a request with an un-supported HTTP Method Axis2/C

[jira] Resolved: (AXIS2C-1007) HTTP HEAD request recieves 200 OK response when it should be failed

[ https://issues.apache.org/jira/browse/AXIS2C-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1007. - Resolution: Fixed Fix Version/s: Current (Nightly) Fixed Issue HTTP HEAD

[jira] Created: (AXIS2C-1054) HTTP Status 404 returned instead of 405, when doing REST calls

Components: transport/http Affects Versions: Current (Nightly) Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: Current (Nightly) HTTP Status 404 returned instead of 405, when doing REST calls. This is due to not having a way to determine

[jira] Resolved: (AXIS2C-1050) When doing rest get '+' is not url encoded

[ https://issues.apache.org/jira/browse/AXIS2C-1050?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1050. - Resolution: Fixed Fix Version/s: Current (Nightly) Assignee: Senaka

Re: Caching support for large attachments

to cache to multiple files rather. Regards, Senaka Hi, In Axis2/Java case we do write the attachment content directly from the InputStream to the File when the attachment size is larger than the threshold. This avoids loading the whole attachment to the memory at all. In this case

Re: Axis2/C 1.3 source compilation error

distributions. Hopefully, I will try to get rid of these warnings too. And, perhaps in the future we can ensure 64-bit support too. Regards, Senaka On Thu, 2008-03-13 at 09:36 +0530, Dinesh Premalal wrote: Samisa Abeysinghe [EMAIL PROTECTED] writes: You seem to have warnings treated as errors. Can

[jira] Created: (AXIS2C-1053) In axutil_duration_t No Initialization is done for the duration struct's members if the values the negative.

://issues.apache.org/jira/browse/AXIS2C-1053 Project: Axis2-C Issue Type: Bug Components: util Affects Versions: 1.3.0 Reporter: Senaka Fernando Assignee: Senaka Fernando Fix For: Current (Nightly) In axutil_duration_t No Initialization

[jira] Resolved: (AXIS2C-1053) In axutil_duration_t No Initialization is done for the duration struct's members if the values the negative.

[ https://issues.apache.org/jira/browse/AXIS2C-1053?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando resolved AXIS2C-1053. - Resolution: Fixed Fixed Issue In axutil_duration_t No Initialization is done

Re: Axis2/C 1.3 source compilation error

axis2_header2.h int foo() { } Regards, Senaka Hi Senaka, After I removed /WX, the compilation does go through successfully. However, when I try to include the deployment in my application, I am getting another compilation error due to type redefinition: x:\inc\i18n\unicode\pwin32.h

Improving REST on Axis2/C

. This will give them more flexibility especially when it comes to PUT/POST requests. If there are any other immediate concerns please let me know. Regards, Senaka - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail

[jira] Commented: (AXIS2C-1049) Axis2/C does not handle timezone offsets or fractional seconds correctly

[ https://issues.apache.org/jira/browse/AXIS2C-1049?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12577469#action_12577469 ] Senaka Fernando commented on AXIS2C-1049: - Hi Dave, Fixed all issues, except

RE: [jira] Commented: (AXIS2C-854) Error in SOAP Action Based Dispatching

Hi Dave, Yes, I was in fact referring to the same question you intended. Seems that this was added [1]. But, it doesn't seem to work. Will take a good look to see if something is altered or whether I missed out on something. [1] https://issues.apache.org/jira/browse/AXIS2C-954 Regards, Senaka

RE: [jira] Commented: (AXIS2C-854) Error in SOAP Action Based Dispatching

Hi again Dave, It is working. You will have to set the action (SOAP or WS-Addressing) to get this thing to work. Regards, Senaka Hi Dave, Yes, I was in fact referring to the same question you intended. Seems that this was added [1]. But, it doesn't seem to work. Will take a good look

Re: TCPMon C Tool now supports resending

Hi Senaka, Please look at the help message w get when run gdb -h command. At the end it says like this For more information, type help from within GDB, or consult the GDB manual (available as on-line info or a printed manual). Report bugs to [EMAIL PROTECTED]. We can use same approach

Solution to Core Dump Issue Raised in User List [was: Re: Core dumps in Axis libraries]

serve. The previous implementation caused this to fail with a segfault. But, with the fix, it will rather not crash but, loop until it gets a chance to serve the request. Could this solve the core dump issue? Regards, Senaka Raghavendra SM wrote: As expected, when I put a delay of about 50

Re: TCPMon C Tool now supports resending

it in the help message. Perhaps a runtime 'h' needs to be provided? Thoughts? Regards, Senaka Hi Senaka, Nice work. It will be better if we can print this option also when using ./tcpmon -h. Also add this to documentation. I test it and it worked fine. Thanks Milinda On Mon, Mar 10, 2008 at 2

Re: Solution to Core Dump Issue Raised in User List [was: Re: Core dumps in Axis libraries]

Senaka Fernando wrote: Hi Samisa, I fixed two bugs regarding stream handling inside simple_http_svr_conn.c. This fixes an issue of this nature. Say, we have two server threads that try to serve requests offered to the axis2 server. Now, according to what is intended, one must serve

Re: Solution to Core Dump Issue Raised in User List [was: Re: Core dumps in Axis libraries]

. However, I didn't have any way to test multiple requests made to a single port from multiple machines. That may be a different scenario. Regards, Senaka Samisa... Senaka Fernando wrote: Senaka Fernando wrote: Hi Samisa, I fixed two bugs regarding stream handling inside simple_http_svr_conn.c

[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-tabpanelfocusedCommentId=12576966#action_12576966 ] Senaka Fernando commented on AXIS2C-1040: - Hi Frank, Will modify

Re: Solution to Core Dump Issue Raised in User List [was: Re: Core dumps in Axis libraries]

a mechanism of retrying, if it does fail which did not work due to the segfault. Regards, Senaka Were you able to re-create the problem without passing -1 to accept? No I was not able to make accept fail without passing -1. Added a printf there to print any failure in accept and it didn't. However

Re: Solution to Core Dump Issue Raised in User List [was: Re: Core dumps in Axis libraries]

, Axis2/C implementation will not cause a SIGTERM inside accept(2) and that should be through the intervention of some external source. Regards, Senaka Samisa... Senaka Fernando wrote: Hi again Samisa, And, also, I don't have any similar database accessing logic etc. Therefore, it is hard

  1   2   3   4   5   6   7   8   >