[jira] Closed: (AXIS2C-742) Improper placement of code in data_handler.c leads to increased time overhead and memory leaks.

[ https://issues.apache.org/jira/browse/AXIS2C-742?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando closed AXIS2C-742. -- Closed Issue Improper placement of code in data_handler.c leads to increased time overhead and

[jira] Closed: (AXIS2C-741) axis2_any_content_type_add_value(...), in any_content_type.c always returns AXIS2_SUCCESS.

[ https://issues.apache.org/jira/browse/AXIS2C-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando closed AXIS2C-741. -- Closed Issue axis2_any_content_type_add_value(...), in any_content_type.c always returns

[jira] Closed: (AXIS2C-788) An error for indicating that an attachment is missing is required.

[ https://issues.apache.org/jira/browse/AXIS2C-788?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando closed AXIS2C-788. -- Closed Issue An error for indicating that an attachment is missing is required.

[jira] Closed: (AXIS2C-743) some return paths in axiom_data_handler_read_from() does not call fclose() on the open file stream, in data_handler.c

[ https://issues.apache.org/jira/browse/AXIS2C-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando closed AXIS2C-743. -- Closed Issue some return paths in axiom_data_handler_read_from() does not call fclose() on the

[jira] Closed: (AXIS2C-775) Improper Exit in echo_non_blocking_dual.c causes memory leak

[ https://issues.apache.org/jira/browse/AXIS2C-775?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando closed AXIS2C-775. -- Closed Issue Improper Exit in echo_non_blocking_dual.c causes memory leak

[jira] Closed: (AXIS2C-773) Bug in op_client.c No Check for NULL.

[ https://issues.apache.org/jira/browse/AXIS2C-773?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando closed AXIS2C-773. -- Closed Issue Bug in op_client.c No Check for NULL. -

[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#action_12547473 ] Senaka Fernando commented on AXIS2C-721: Hi Dushshantha, What I mean is, since, we want to make Axis2/C

[jira] Closed: (AXIS2C-739) Function Definition does not match declaration in soap_builder.c

[ https://issues.apache.org/jira/browse/AXIS2C-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando closed AXIS2C-739. -- Close Issue Function Definition does not match declaration in soap_builder.c

[jira] Updated: (AXIS2C-765) Include exact download location for libxml2 in docs

[ https://issues.apache.org/jira/browse/AXIS2C-765?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Senaka Fernando updated AXIS2C-765: --- Attachment: diff.txt Refer diff.txt for proposed modifications to the current svn. Also, I

Re: AXISFault

java.net.SocketException: Connection reset Exception occurs in client side, when the client can not establish a connection with the server. ex: if the server is running foo.com:8790 and client tries foo.com:8791. Thus, check if the server is running or if the client end point address is correct.

[jira] Commented: (AXIS2-3353) Use wrapper types when elements are optional (i.e.: nillable=true or minOccurs=0/maxOccurs=1)

[ https://issues.apache.org/jira/browse/AXIS2-3353?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_12547456 ] Stein Henriksen commented on AXIS2-3353: I also have the same problem using minOccurs=0 when running

[jira] Created: (AXIS2-3382) NPE throws when invoking jax-ws calculator sample service

NPE throws when invoking jax-ws calculator sample service - Key: AXIS2-3382 URL: https://issues.apache.org/jira/browse/AXIS2-3382 Project: Axis 2.0 (Axis2) Issue Type: Bug

Re: AXISFault

Where is this exception generated? Server side generates and you sees this in client side or is this only in client side? If server generates this exception, then server is trying to connect to the client, which it shouldn't, and having this trouble. Please check the WSDL of the web service

Re: [Axis2]: Using Axis2 with Tomcat v4.1.27

Hi Jan, Axis2 1.3 will work with Tomcat server 4.1.27, I do not have any doubt on that. But I strongly recommend you to use Tomcat 5.x version, especially if you are working with JDK 1.5. IIRC, Tomcat 5.0.x version works with JDK 1.4. Why I recommend is that, one of the tomcat developers