Re: Axis2C support for dynamic operations

Dave Meier wrote: Hi Samisa, Is there any way to do the equivalent of "any" for a service? Kind of like an "any" element in a schema, except for an operation. All I need is to have the engine call my invoke method and at that point I can write all the code that knows how to handle the operatio

md5 in tools?

I see that md5 implementation has been placed in tools, with separate build system. Should it not go to utl? It is a utility that we would use, and not a tool like tcpmon. Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL P

Re: version incompatibilities

Hi, Samisa Abeysinghe <[EMAIL PROTECTED]> writes: > Oops! That is a glitch :( > > We should add this to our check list in the release process Wiki. I updated wiki with the files that we need to update version numbers, before every release. If you think any file that need to be in that list pleas

[jira] Commented: (AXIS2C-936) On incomplete response message, the client receives response data for the elements up to the error, but no indication of the error

[ https://issues.apache.org/jira/browse/AXIS2C-936?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563044#action_12563044 ] Bill Mitchell commented on AXIS2C-936: -- Looking at this again in the log, it would be

[jira] Commented: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault

[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12563043#action_12563043 ] Bill Mitchell commented on AXIS2C-933: -- The issue I alluded to above, that after apply

[jira] Created: (AXIS2C-936) On incomplete response message, the client receives response data for the elements up to the error, but no indication of the error

On incomplete response message, the client receives response data for the elements up to the error, but no indication of the error -- Key: AXIS2C-936

[jira] Updated: (AXIS2C-818) If the returned message read fills the buffer, http_transport_utils.c clobbers the byte past the end of the buffer

[ https://issues.apache.org/jira/browse/AXIS2C-818?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Mitchell updated AXIS2C-818: - Description: If the returned message from libcurl exceeds 4096 characters, the size of a guththi

[jira] Updated: (AXIS2C-935) Support for RESTful Services

[ https://issues.apache.org/jira/browse/AXIS2C-935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-935: --- Attachment: diff_rest.txt Refer diff_rest.txt for patch that adds support for GET, POST and H

[jira] Created: (AXIS2C-935) Support for RESTful Services

Support for RESTful Services Key: AXIS2C-935 URL: https://issues.apache.org/jira/browse/AXIS2C-935 Project: Axis2-C Issue Type: Improvement Components: core/context, core/deployment, core/description,

Template Matching for Query String in RESTful Services

Hi all, I'm almost done with template matching for request URL in RESTful Services. However, I have left out the Query String when I do the matching for the moment. This is due to several reasons. 1. The query parameters are already made available on the generated payload. 2. The order of params

[jira] Commented: (AXIS2C-933) guththila parser does not handle incomplete messages well, leading to an infinite loop or seg fault

[ https://issues.apache.org/jira/browse/AXIS2C-933?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12562971#action_12562971 ] Supun Kamburugamuva commented on AXIS2C-933: There is another thing that I coul

[jira] Updated: (AXIS2C-934) Organize Test Cases

[ https://issues.apache.org/jira/browse/AXIS2C-934?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-934: --- Description: Hi all, recently we've added several test_cases, especially to util. They all d

[jira] Created: (AXIS2C-934) Organize Test Cases

Organize Test Cases --- Key: AXIS2C-934 URL: https://issues.apache.org/jira/browse/AXIS2C-934 Project: Axis2-C Issue Type: Task Components: tests Affects Versions: Current (Nightly) Reporter: Senaka