[jira] Resolved: (AXIS2C-568) Issues in the Axis2/C Manual - Quick Start Guide

[ https://issues.apache.org/jira/browse/AXIS2C-568?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-568. -- Resolution: Fixed Fixed the issues pointed out. Many thanks to Evanthika

[jira] Resolved: (AXIS2C-267) Drop use of macros in method calls to improve backward compatibility of binary

[ https://issues.apache.org/jira/browse/AXIS2C-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-267. -- Resolution: Fixed After a long struggle, macros has been dropped form all possible

Re: [Axis2] Time for 1.0 Release

As a C project, I would suggest that it might make sense for Axis2/C to follow the lead of other major Apache C projects, such as APR and httpd. These two have fairly detailed versioning guidelines and requirements, especially in relation to the promise of stable APIs and ABIs,

[jira] Assigned: (AXIS2C-192) Document how to use proxy

[ https://issues.apache.org/jira/browse/AXIS2C-192?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-192: Assignee: Dinesh Premalal Document how to use proxy

[jira] Updated: (AXIS2C-244) Provide multiple entry points to a single DLL so that 1-1 relationship between dlls and interface implementations can avoided.

[ https://issues.apache.org/jira/browse/AXIS2C-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-244: - Fix Version/s: (was: 1.0.0) This have to be moved to post 1.0 as we cannot afford

[jira] Updated: (AXIS2C-243) utils have dependancies on axis2 core when it comes to class loading

[ https://issues.apache.org/jira/browse/AXIS2C-243?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-243: - Fix Version/s: (was: 1.0.0) This issue too has to be moved to post 1.0 utils have

[jira] Updated: (AXIS2C-245) Versioning of DLLs

[ https://issues.apache.org/jira/browse/AXIS2C-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-245: - Fix Version/s: (was: 1.0.0) Moved to post 1.0 Versioning of DLLs

[jira] Resolved: (AXIS2C-409) Memory allocated by gethostbyname not released

[ https://issues.apache.org/jira/browse/AXIS2C-409?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-409. -- Resolution: Won't Fix This appears to be a windows problem, does not happen on Linux

[Axis2] Moving Woden and XMLSchema to scratch

A while ago we discusses over this list that we would not ship Woden and XMLSchema with 1.0 release. So I am going to move them to scratch area for the time being. Thanks, Samisa... - To unsubscribe, e-mail: [EMAIL

[jira] Resolved: (AXIS2C-473) Statically allocate ops structs

[ https://issues.apache.org/jira/browse/AXIS2C-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-473. -- Resolution: Fixed After a long struggle, finally the ops struct is either removed

Re: [Axis2]TCP Transport for Axis2/C

Dinesh Premalal wrote: Hi Devs, I'm interested in doing a TCP Transport for Axis2/C. I have some questions to figure out. Absolute +1. But after 1.0 please ;) 1. Is there any ways to access TCP socket (actually , the socket that need to read stream), from httpd.

[Axis2] Cod freeze for 1.0

Hi All, I would like to call upon a code freeze as far as new features and functionality is concerned. I propose that we do this freeze form next Monday 02nd April 2007. We have to do some more stuff such as binary compatibility and release numbering changes. Apart form that, I

Re: [Axis2]TCP Transport for Axis2/C

1. Is there any ways to access TCP socket (actually , the socket that need to read stream), from httpd. There are an array of modules for Apache2 that supports other protocols; FTP, SMTP, POP3 etc. Having a peek into the source code, it seems that they are using some filtering

[jira] Assigned: (AXIS2C-448) axiom_xml_writer_create opened file can't be closed correctly

[ https://issues.apache.org/jira/browse/AXIS2C-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-448: Assignee: Samisa Abeysinghe axiom_xml_writer_create opened file can't be closed

[jira] Resolved: (AXIS2C-448) axiom_xml_writer_create opened file can't be closed correctly

[ https://issues.apache.org/jira/browse/AXIS2C-448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-448. -- Resolution: Fixed Added AXIOM_XML_WRITER_FLUSH method to help clean up

[jira] Resolved: (AXIS2C-447) AXIOM_STAX_BUILDER_FREE releases built document

[ https://issues.apache.org/jira/browse/AXIS2C-447?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-447. -- Resolution: Fixed Assignee: Samisa Abeysinghe A workaroud for this is to set

[jira] Updated: (AXIS2C-410) custom URL prefixes not allowed

[ https://issues.apache.org/jira/browse/AXIS2C-410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-410: - Fix Version/s: (was: 1.0.0) This needs more work to fix as we have failed to apply

[jira] Updated: (AXIS2C-262) mod_axis2 should allow username token passwords to be validated used Apache's authn_providers

[ https://issues.apache.org/jira/browse/AXIS2C-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-262: - Does not look like we would be able to do this before 1.0 mod_axis2 should allow username

[jira] Updated: (AXIS2C-262) mod_axis2 should allow username token passwords to be validated used Apache's authn_providers

[ https://issues.apache.org/jira/browse/AXIS2C-262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-262: - Fix Version/s: (was: 1.0.0) mod_axis2 should allow username token passwords

[jira] Resolved: (AXIS2C-121) Log implementation does not go through ops

[ https://issues.apache.org/jira/browse/AXIS2C-121?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-121. -- Resolution: Fixed Assignee: Samisa Abeysinghe (was: Dinesh Premalal) It goes

[jira] Updated: (AXIS2C-401) Signal Handling in windows

[ https://issues.apache.org/jira/browse/AXIS2C-401?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-401: - Fix Version/s: (was: 1.0.0) We have to move this to be a post 1.0. No one is working

[jira] Assigned: (AXIS2C-473) Statically allocate ops structs

[ https://issues.apache.org/jira/browse/AXIS2C-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-473: Assignee: Samisa Abeysinghe Statically allocate ops structs

[jira] Commented: (AXIS2C-553) axiom_element_get_first_child_with_qname method is not working as expected.

[ https://issues.apache.org/jira/browse/AXIS2C-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484736 ] Samisa Abeysinghe commented on AXIS2C-553: -- After the latest fixes, can we consider this done? Do we have

[jira] Resolved: (AXIS2C-536) Sock handle and mem leak in axis2_soap_over_http_sender_send

[ https://issues.apache.org/jira/browse/AXIS2C-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-536. -- Resolution: Fixed Fixed to free the client Sock handle and mem leak

[jira] Resolved: (AXIS2C-269) Try to clean up axis2_stream

[ https://issues.apache.org/jira/browse/AXIS2C-269?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-269. -- Resolution: Fixed Added flush and close as well. Other issues were also resolved

[jira] Commented: (AXIS2C-278) Check for and eliminate use of non-thread-safe library functions

[ https://issues.apache.org/jira/browse/AXIS2C-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484783 ] Samisa Abeysinghe commented on AXIS2C-278: -- The main problamatic uses are caused by the use

[jira] Resolved: (AXIS2C-278) Check for and eliminate use of non-thread-safe library functions

[ https://issues.apache.org/jira/browse/AXIS2C-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-278. -- Resolution: Fixed As per the previous comments, bulk of the code base do not use non

[jira] Resolved: (AXIS2C-553) axiom_element_get_first_child_with_qname method is not working as expected.

[ https://issues.apache.org/jira/browse/AXIS2C-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-553. -- Resolution: Fixed Solved the problem by using qname equals

Re: [jira] Created: (AXIS2C-572) remove method axis2_options_set_soap_action and add that behavior to axis2_options_set_action

Jira is down - hence replying via mail SOAP action and addressing action are not the same. Hence this issue is not valid. Samisa... Nandika Jayawardana (JIRA) wrote: remove method axis2_options_set_soap_action and add that behavior to axis2_options_set_action

[jira] Commented: (AXIS2C-572) remove method axis2_options_set_soap_action and add that behavior to axis2_options_set_action

[ https://issues.apache.org/jira/browse/AXIS2C-572?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484920 ] Samisa Abeysinghe commented on AXIS2C-572: -- I do not think this issue is valid. WS-Addressing action

[jira] Assigned: (AXIS2C-226) Remove the MEP client from API and move the relavant logic to operation client

[ https://issues.apache.org/jira/browse/AXIS2C-226?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-226: Assignee: Samisa Abeysinghe Remove the MEP client from API and move the relavant

Re: [Axis2C] Compiling head

Simon Elbaz wrote: Hi, I have met some problems to compile the axis2c head. Here are the modifications done to get all (almost) in order: 1- upgrade of the libxml2 library (2.6.27) 2- some modifications (cf. patch.diff) Patch applied. Many thanks for the patch. Samisa...

Re: [Sandesha/C] Broken svn head

Chintana Wilamuna wrote: Hi, I couldn't compile Sandesha/C svn head. The code was not updated according to the changes in Axis2/C. According to Damitha the extra boolean AXIS2_FALSE is no longer used in axis2_msg_ctx_{get,set}_property functions. Attached patch fix the issues. Kindly send

Re: [Sandesha/C] Broken svn head

Samisa Abeysinghe wrote: Chintana Wilamuna wrote: Hi, I couldn't compile Sandesha/C svn head. The code was not updated according to the changes in Axis2/C. According to Damitha the extra boolean AXIS2_FALSE is no longer used in axis2_msg_ctx_{get,set}_property functions. Attached patch

[jira] Resolved: (AXIS2C-485) Refactor om_output write method to improve performance

[ https://issues.apache.org/jira/browse/AXIS2C-485?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-485. -- Resolution: Fixed Fixed by improving the serialize logic Refactor om_output write

[jira] Resolved: (AXIS2C-444) Add a fault handling sample to show how to deal with SOAP faults

[ https://issues.apache.org/jira/browse/AXIS2C-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-444. -- Resolution: Fixed Google sample now has some fault handling logic that can serve

[jira] Assigned: (AXIS2C-444) Add a fault handling sample to show how to deal with SOAP faults

[ https://issues.apache.org/jira/browse/AXIS2C-444?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-444: Assignee: Samisa Abeysinghe (was: Sanjaya Ratnaweera) Add a fault handling

[jira] Resolved: (AXIS2C-498) Axiom OM structure built is inconsistent with the original xml document in certain cases where the default namespace is set to the empty namespace

[ https://issues.apache.org/jira/browse/AXIS2C-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-498. -- Resolution: Fixed Someone has applied the given patch Axiom OM structure built

[jira] Commented: (AXIS2C-497) Wrong content type doesn't give proper fault

[ https://issues.apache.org/jira/browse/AXIS2C-497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12484263 ] Samisa Abeysinghe commented on AXIS2C-497: -- I think choosing default Content-Type and going ahead would

[jira] Assigned: (AXIS2C-170) Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object.

[ https://issues.apache.org/jira/browse/AXIS2C-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-170: Assignee: Samisa Abeysinghe (was: Damitha Kumarage) Compact the if blocks

[jira] Resolved: (AXIS2C-170) Compact the if blocks into one if block in create_dll method so that the lib is loaded into a void object.

[ https://issues.apache.org/jira/browse/AXIS2C-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-170. -- Resolution: Fixed Removed unwanted if blocks Compact the if blocks into one if block

[jira] Assigned: (AXIS2C-257) free methods should return void not axis2_status_t

[ https://issues.apache.org/jira/browse/AXIS2C-257?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-257: Assignee: Samisa Abeysinghe (was: Sanjaya Ratnaweera) free methods should return

[jira] Resolved: (AXIS2C-544) Axis2-C Engine doesn't return an AXIS2_FAILURE when an in_handler gives failure in client side

[ https://issues.apache.org/jira/browse/AXIS2C-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-544. -- Resolution: Fixed There was a bug in engine receive and context handler

[jira] Assigned: (AXIS2C-360) engaging a module which is already engaged

[ https://issues.apache.org/jira/browse/AXIS2C-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-360: Assignee: Samisa Abeysinghe engaging a module which is already engaged

[jira] Resolved: (AXIS2C-360) engaging a module which is already engaged

[ https://issues.apache.org/jira/browse/AXIS2C-360?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-360. -- Resolution: Fixed Fixed so that it returns AXIS2_FAILURE on engaging an already

[jira] Resolved: (AXIS2C-207) Remove persistent non-persistent logic from ctx

[ https://issues.apache.org/jira/browse/AXIS2C-207?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-207. -- Resolution: Fixed logic removed Remove persistent non-persistent logic from ctx

[jira] Commented: (AXIS2C-360) engaging a module which is already engaged

[ https://issues.apache.org/jira/browse/AXIS2C-360?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483558 ] Samisa Abeysinghe commented on AXIS2C-360: -- When you say programmatically, using which functions? On client

Re: [Axis2][VOTE] Move Rampart/C out of Axis2/C

Kaushalye Kapuruge wrote: Hi, Yes. We need a separate JIRA page. But for a mail discussions I think Axis2/C lists are more applicable. Java users/devs are less attractive to Ramaprt/C discussions than Axis2/C users/devs. I tought Rampart had a seperate mailing list other than Axis Java

[jira] Assigned: (AXIS2C-553) axiom_element_get_first_child_with_qname method is not working as expected.

[ https://issues.apache.org/jira/browse/AXIS2C-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-553: Assignee: Samisa Abeysinghe axiom_element_get_first_child_with_qname method

[jira] Commented: (AXIS2C-553) axiom_element_get_first_child_with_qname method is not working as expected.

[ https://issues.apache.org/jira/browse/AXIS2C-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483128 ] Samisa Abeysinghe commented on AXIS2C-553: -- I have done a small fix. Can you please see if it is OK now

[jira] Assigned: (AXIS2C-414) svc_skeleton-ops-init is never called

[ https://issues.apache.org/jira/browse/AXIS2C-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-414: Assignee: Samisa Abeysinghe svc_skeleton-ops-init is never called

[jira] Resolved: (AXIS2C-414) svc_skeleton-ops-init is never called

[ https://issues.apache.org/jira/browse/AXIS2C-414?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-414. -- Resolution: Fixed Fixed logic in message receiver to call svc_skeleton init once per

[jira] Resolved: (AXIS2C-254) ops structs should be statically-allocated and shared

[ https://issues.apache.org/jira/browse/AXIS2C-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-254. -- Resolution: Duplicate Same as AXIS2C-473 ops structs should be statically-allocated

[jira] Resolved: (AXIS2C-550) Install form source on Windows doc has bugs

[ https://issues.apache.org/jira/browse/AXIS2C-550?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-550. -- Resolution: Fixed Assignee: Samisa Abeysinghe Fixed links Install form source

[jira] Updated: (AXIS2C-561) WSDL2C: WSDL Choice element not handled

[ https://issues.apache.org/jira/browse/AXIS2C-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-561: - Fix Version/s: (was: 0.96) Priority: Major (was: Blocker) WSDL2C: WSDL

[jira] Assigned: (AXIS2C-156) It will be helpful to have a method for check the soap fault of the response from the service client

[ https://issues.apache.org/jira/browse/AXIS2C-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-156: Assignee: Samisa Abeysinghe (was: Dinesh Premalal) It will be helpful to have

[jira] Resolved: (AXIS2C-156) It will be helpful to have a method for check the soap fault of the response from the service client

[ https://issues.apache.org/jira/browse/AXIS2C-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-156. -- Resolution: Fixed Added API calls to check if there is a fault form last call and also

[jira] Commented: (AXIS2C-553) axiom_element_get_first_child_with_qname method is not working as expected.

[ https://issues.apache.org/jira/browse/AXIS2C-553?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12483396 ] Samisa Abeysinghe commented on AXIS2C-553: -- Can you please provide a code sample of what you are doing when

Re: [Axis2][VOTE] Move Rampart/C out of Axis2/C

Kaushalye Kapuruge wrote: Hi, I don't think dropping Rampart/C questions in the java list is a good idea. We need separate mailing list for Rampart/C. Until then we can use Axis2/C mailing list and JIRA as we used to. For Sandesha/C, mails go over the same list with a subject prefix.

Re: [Axis2][VOTE] Move Rampart/C out of Axis2/C

+1. Samisa... Kaushalye Kapuruge wrote: Hi List, Since Rampart/C works as a module for Axis2/C and it is not part of the Axis2/C engine, I propose that we move Rampart/C out of Axis2/C project and place it under http://svn.apache.org/repos/asf/webservices/rampart/trunk/c/ This groups

[jira] Resolved: (AXIS2C-239) Wrong fault message is serialized when sending a soap11 fault

[ https://issues.apache.org/jira/browse/AXIS2C-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-239. -- Resolution: Fixed I have fixed the logic to convert the fault to SOAP 1.1 format

[jira] Resolved: (AXIS2C-265) axis2_string.h macro strangeness

[ https://issues.apache.org/jira/browse/AXIS2C-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-265. -- Resolution: Fixed Macros has been dropped form sting header axis2_string.h macro

[jira] Assigned: (AXIS2C-239) Wrong fault message is serialized when sending a soap11 fault

[ https://issues.apache.org/jira/browse/AXIS2C-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-239: Assignee: Samisa Abeysinghe (was: Dinesh Premalal) Wrong fault message

[jira] Updated: (AXIS2C-201) parsing schemas read from url need to be supported. Currently it only reads imported schemas from doc base uri

[ https://issues.apache.org/jira/browse/AXIS2C-201?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-201: - Fix Version/s: (was: 1.0.0) Assignee: (was: Sanjaya Ratnaweera

[jira] Updated: (AXIS2C-210) Have some docs for Woden

[ https://issues.apache.org/jira/browse/AXIS2C-210?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-210: - Fix Version/s: (was: 1.0.0) wont be fixed for 1.0 Have some docs for Woden

[jira] Updated: (AXIS2C-211) Have some docs for XML/Schema

[ https://issues.apache.org/jira/browse/AXIS2C-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-211: - Fix Version/s: (was: 1.0.0) Assignee: (was: Sanjaya Ratnaweera) Would

[jira] Updated: (AXIS2C-224) Calculator server sample need to be changed

[ https://issues.apache.org/jira/browse/AXIS2C-224?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-224: - Fix Version/s: (was: 1.0.0) Assignee: (was: Dinesh Premalal

[jira] Commented: (AXIS2C-378) can't keep the connection alive for HTTP 1.1 on client side

[ https://issues.apache.org/jira/browse/AXIS2C-378?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482582 ] Samisa Abeysinghe commented on AXIS2C-378: -- Can this be achieved with LibCurl transport? If so we can close

[jira] Assigned: (AXIS2C-378) can't keep the connection alive for HTTP 1.1 on client side

[ https://issues.apache.org/jira/browse/AXIS2C-378?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-378: Assignee: Dinesh Premalal can't keep the connection alive for HTTP 1.1 on client

[Axis2] Libcurl solved this? - (AXIS2C-378) can't keep the connection alive for HTTP 1.1 on client side

Hi Dinesh, Given that you are the one who implemented libCurl transport, you are the best guy to comment this. If we use mod_axis2 with httpd and libCurl based transport, would keepalive be managed properly? Thanks, Samisa... Samisa Abeysinghe (JIRA) wrote: [ https

[jira] Commented: (AXIS2C-359) Seg faults with reconnecting the Tomcat Server by calling axis2_stub_create_with_endpoint_ref_and_client_home

[ https://issues.apache.org/jira/browse/AXIS2C-359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482588 ] Samisa Abeysinghe commented on AXIS2C-359: -- I hope with 0.96 release, this problem must have been solved

[jira] Resolved: (AXIS2C-359) Seg faults with reconnecting the Tomcat Server by calling axis2_stub_create_with_endpoint_ref_and_client_home

[ https://issues.apache.org/jira/browse/AXIS2C-359?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-359. -- Resolution: Fixed reuse of service client was fixed in 0.96. Also one can use

[jira] Closed: (AXIS2C-310) simple axis server segfaults at termination when RM is engaged

[ https://issues.apache.org/jira/browse/AXIS2C-310?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe closed AXIS2C-310. Resolution: Fixed Assignee: Samisa Abeysinghe (was: Damitha Kumarage) Some commit

[jira] Commented: (AXIS2C-485) Refactor om_output write method to improve performance

[ https://issues.apache.org/jira/browse/AXIS2C-485?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482596 ] Samisa Abeysinghe commented on AXIS2C-485: -- This has been fixed but have introduced a bug in case

[jira] Updated: (AXIS2C-232) WODEN/C fails parsing some WSDLs

[ https://issues.apache.org/jira/browse/AXIS2C-232?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-232: - Fix Version/s: (was: 1.0.0) Would not be fixed for 1.0 WODEN/C fails parsing some

[jira] Updated: (AXIS2C-420) No implementations for some XML Data Types in World Wide Web Consortium (W3C) XML Schema Part 2: DataTypes Spec

[ https://issues.apache.org/jira/browse/AXIS2C-420?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-420: - Fix Version/s: (was: 1.0.0) No implementations for some XML Data Types in World

[jira] Updated: (AXIS2C-428) http_client reads data from a socket without checking weather the socket is ready to give data. If the data arrived and socket is not ready client assumes data is not avai

[ https://issues.apache.org/jira/browse/AXIS2C-428?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-428: - Fix Version/s: (was: 1.0.0) It is almost impossible to reproduce this with normal

[jira] Assigned: (AXIS2C-426) echo_blocking_dual, echo_non_blocking_dual and mtom sample clients hang on Windows after giving the result correctly

[ https://issues.apache.org/jira/browse/AXIS2C-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe reassigned AXIS2C-426: Assignee: Samisa Abeysinghe echo_blocking_dual, echo_non_blocking_dual and mtom

[jira] Resolved: (AXIS2C-426) echo_blocking_dual, echo_non_blocking_dual and mtom sample clients hang on Windows after giving the result correctly

[ https://issues.apache.org/jira/browse/AXIS2C-426?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-426. -- Resolution: Fixed Now all of them exit properly echo_blocking_dual

[jira] Updated: (AXIS2C-228) Woden/C doesnt provide the correct MEP for WSDL1.0

[ https://issues.apache.org/jira/browse/AXIS2C-228?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-228: - Fix Version/s: (was: 1.0.0) Would not be fixed for 1.0 Woden/C doesnt provide

[jira] Updated: (AXIS2C-291) Consider introducing higher-level memory management abstractions

[ https://issues.apache.org/jira/browse/AXIS2C-291?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-291: - Fix Version/s: (was: 1.0.0) We really make use of APR pools in Apche2 module

[jira] Updated: (AXIS2C-557) WSDL2C: generated adb code does not allow any elements to be omitted - too inflexible

[ https://issues.apache.org/jira/browse/AXIS2C-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-557: - Fix Version/s: (was: Current (Nightly)) Priority: Major (was: Blocker

[jira] Updated: (AXIS2C-546) IIS filter module needs to be made to work with IIS 6

[ https://issues.apache.org/jira/browse/AXIS2C-546?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-546: - Fix Version/s: (was: Current (Nightly)) IIS filter module needs to be made to work

[Axis2] Issues AXIS2C-551, AXIS2C-542 and AXIS2C-557

Hi Milinda, Could you please look into the above mentioned issues and let us know if you would be able to fix them. Please add your comments in Jira. Thanks, Samisa... Samisa Abeysinghe (JIRA) wrote: [ https://issues.apache.org/jira/browse/AXIS2C-551?page

[jira] Closed: (AXIS2C-36) Add IPv6 support for HTTP (and TCP) transport

[ https://issues.apache.org/jira/browse/AXIS2C-36?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe closed AXIS2C-36. --- Resolution: Fixed Fix Version/s: 1.0.0 Assignee: (was: Sahan Gamage

[jira] Updated: (AXIS2C-536) Sock handle and mem leak in axis2_soap_over_http_sender_send

[ https://issues.apache.org/jira/browse/AXIS2C-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-536: - Fix Version/s: 1.0.0 Sock handle and mem leak in axis2_soap_over_http_sender_send

[jira] Updated: (AXIS2C-537) Severe memory leak in process_http_post_request

[ https://issues.apache.org/jira/browse/AXIS2C-537?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-537: - Fix Version/s: 1.0.0 Severe memory leak in process_http_post_request

[jira] Updated: (AXIS2C-254) ops structs should be statically-allocated and shared

[ https://issues.apache.org/jira/browse/AXIS2C-254?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-254: - Fix Version/s: 1.0.0 ops structs should be statically-allocated and shared

[jira] Closed: (AXIS2C-256) Overuse of OO types

[ https://issues.apache.org/jira/browse/AXIS2C-256?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe closed AXIS2C-256. Resolution: Fixed Fix Version/s: 1.0.0 Bulk of the overuse of OO has been dropped

[jira] Updated: (AXIS2C-267) Drop use of macros in method calls to improve backward compatibility of binary

[ https://issues.apache.org/jira/browse/AXIS2C-267?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-267: - Fix Version/s: 1.0.0 Drop use of macros in method calls to improve backward

[jira] Updated: (AXIS2C-493) Improve SOAP Body based dispatcher to look for namespace of the first element

[ https://issues.apache.org/jira/browse/AXIS2C-493?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-493: - Fix Version/s: 1.0.0 Improve SOAP Body based dispatcher to look for namespace

[jira] Updated: (AXIS2C-544) Axis2-C Engine doesn't return an AXIS2_FAILURE when an in_handler gives failure in client side

[ https://issues.apache.org/jira/browse/AXIS2C-544?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-544: - Fix Version/s: 1.0.0 Axis2-C Engine doesn't return an AXIS2_FAILURE when an in_handler

[jira] Updated: (AXIS2C-473) Statically allocate ops structs

[ https://issues.apache.org/jira/browse/AXIS2C-473?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-473: - Fix Version/s: 1.0.0 Statically allocate ops structs

[jira] Updated: (AXIS2C-498) Axiom OM structure built is inconsistent with the original xml document in certain cases where the default namespace is set to the empty namespace

[ https://issues.apache.org/jira/browse/AXIS2C-498?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-498: - Fix Version/s: 1.0.0 Axiom OM structure built is inconsistent with the original xml

[jira] Updated: (AXIS2C-293) Introduce string object

[ https://issues.apache.org/jira/browse/AXIS2C-293?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-293: - Fix Version/s: 1.0.0 Introduce string object

[jira] Updated: (AXIS2C-553) axiom_element_get_first_child_with_qname method is not working as expected.

[ https://issues.apache.org/jira/browse/AXIS2C-553?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-553: - Fix Version/s: 1.0.0 axiom_element_get_first_child_with_qname method is not working

[jira] Updated: (AXIS2C-517) Improvement/Fix for Installation Guide docs on mod_axis2

[ https://issues.apache.org/jira/browse/AXIS2C-517?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe updated AXIS2C-517: - Fix Version/s: 1.0.0 Assignee: Sanjaya Ratnaweera Improvement/Fix

[Axis2] Jira Issues for 1.0

Hi All, I went through all pending issues and marked the issues that I thought that must be fixed for 1.0 release. Please review them and help fix them. Apart form those issues, there are some more stuff to be done before 1.0, including defining the release versioning policies and

[jira] Resolved: (AXIS2C-551) WSDL2C: generated code does not handle optional elements

[ https://issues.apache.org/jira/browse/AXIS2C-551?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-551. -- Resolution: Fixed Fix Version/s: 1.0.0 Milinda has fixed this WSDL2C

[jira] Resolved: (AXIS2C-542) [Axis2] WSDL2C problem when wsdl type name contains - characters

[ https://issues.apache.org/jira/browse/AXIS2C-542?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Samisa Abeysinghe resolved AXIS2C-542. -- Resolution: Fixed Fix Version/s: 1.0.0 Milinda has fixed it [Axis2] WSDL2C

<    3   4   5   6   7   8   9   10   11   12   >