next release / open jiras

Hello Nadir, What are your current 1.6 release prospects? Do you have a tentative timeline first for a release candidate and then a real release? Will AXISCPP (given the advent of AXISC) be dead after 1.6 or can we expect 1.6.1 or even (gasp) 1.7? Which JIRAs do you plan to work on before

[jira] Commented: (AXIS2C-503) Provide Makefile and vc projects for samples in win32-bin

[ https://issues.apache.org/jira/browse/AXIS2C-503?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12482386 ] Dushshantha Chandradasa commented on AXIS2C-503: I added vc projects to ide/vc/samples folder. We

[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 in

[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 is

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

WSDL2C: generated adb code does not allow any elements to be omitted - too inflexible - Key: AXIS2C-557 URL: https://issues.apache.org/jira/browse/AXIS2C-557

[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) This

[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: [

[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 the

[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 of

[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 the

[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, that

[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: [

[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) On

[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 of the

[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] Commented: (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:comment-tabpanel#action_12482642 ] Milinda Lakmal Pathirage commented on AXIS2C-551: - The above suggestion will fix the bug. I think we

[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 for

[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] Commented: (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:comment-tabpanel#action_12482647 ] Milinda Lakmal Pathirage commented on AXIS2C-551: - Bug fixed in latest Axis2 svn trunk. WSDL2C:

[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

[jira] Commented: (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:comment-tabpanel#action_12482656 ] Milinda Lakmal Pathirage commented on AXIS2C-542: - Bug fixed in latest svn head by changing String

[jira] Updated: (AXIS2C-519) [Axis2] axis2_svc_client_create_for_dynamic_invocation returns NULL

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