[jira] Commented: (AXIS2-4460) Axis2 Trunk Does Not Build From a Clean Maven Repo

[ https://issues.apache.org/jira/browse/AXIS2-4460?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12805766#action_12805766 ] Ruwan Linton commented on AXIS2-4460: - I think this issue occurs when running without

[jira] Commented: (AXIS2-4560) Axis2 Asynchronouse web services over TLS

[ https://issues.apache.org/jira/browse/AXIS2-4560?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12781784#action_12781784 ] Ruwan Linton commented on AXIS2-4560: - Isuru, nhttp transport has not been moved from

[jira] Commented: (AXIS2-4552) TransportListener#init called twice on the same instance

[ https://issues.apache.org/jira/browse/AXIS2-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12778850#action_12778850 ] Ruwan Linton commented on AXIS2-4552: - Amila, if you carefully look at the addListener

[jira] Commented: (AXIS2-4304) Improve the ListenerManager startup behavior

[ https://issues.apache.org/jira/browse/AXIS2-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777908#action_12777908 ] Ruwan Linton commented on AXIS2-4304: - Andreas, It cannot be a regression caused by the

[jira] Commented: (AXIS2-4552) TransportListener#init called twice on the same instance

[ https://issues.apache.org/jira/browse/AXIS2-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777907#action_12777907 ] Ruwan Linton commented on AXIS2-4552: - If you carefully look at the current

[jira] Issue Comment Edited: (AXIS2-4304) Improve the ListenerManager startup behavior

[ https://issues.apache.org/jira/browse/AXIS2-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777908#action_12777908 ] Ruwan Linton edited comment on AXIS2-4304 at 11/14/09 12:41 PM:

[jira] Commented: (AXIS2-4552) TransportListener#init called twice on the same instance

[ https://issues.apache.org/jira/browse/AXIS2-4552?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12777931#action_12777931 ] Ruwan Linton commented on AXIS2-4552: - Andreas, I searched through the code to find any

[jira] Assigned: (AXIS2-4306) Extending Axis2 API to add deployers programmatically

[ https://issues.apache.org/jira/browse/AXIS2-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruwan Linton reassigned AXIS2-4306: --- Assignee: Ruwan Linton Extending Axis2 API to add deployers programmatically

[jira] Resolved: (AXIS2-4306) Extending Axis2 API to add deployers programmatically

[ https://issues.apache.org/jira/browse/AXIS2-4306?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruwan Linton resolved AXIS2-4306. - Resolution: Fixed Applied the patch.., thanks Sameera Extending Axis2 API to add deployers

[jira] Updated: (AXIS2-4304) Improve the ListenerManager startup behavior

[ https://issues.apache.org/jira/browse/AXIS2-4304?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruwan Linton updated AXIS2-4304: Attachment: listener-manager.patch This patch fixes the issues for synapse, please do a review and

[jira] Created: (AXIS2-4304) Improve the ListenerManager startup behavior

Improve the ListenerManager startup behavior Key: AXIS2-4304 URL: https://issues.apache.org/jira/browse/AXIS2-4304 Project: Axis 2.0 (Axis2) Issue Type: Improvement Components: kernel

[jira] Created: (AXIS2-3757) Miss behaviour in adding handlers to the phase when the handler has after attribute

Miss behaviour in adding handlers to the phase when the handler has after attribute --- Key: AXIS2-3757 URL: https://issues.apache.org/jira/browse/AXIS2-3757 Project:

[jira] Updated: (AXIS2-3757) Miss behaviour in adding handlers to the phase when the handler has after attribute

[ https://issues.apache.org/jira/browse/AXIS2-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruwan Linton updated AXIS2-3757: Attachment: phase_test.patch This patch provides a testcase for this issue and this patches the

[jira] Updated: (AXIS2-3757) Miss behaviour in adding handlers to the phase when the handler has after attribute

[ https://issues.apache.org/jira/browse/AXIS2-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruwan Linton updated AXIS2-3757: Attachment: (was: phase_test.patch) Miss behaviour in adding handlers to the phase when the

[jira] Updated: (AXIS2-3757) Miss behaviour in adding handlers to the phase when the handler has after attribute

[ https://issues.apache.org/jira/browse/AXIS2-3757?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Ruwan Linton updated AXIS2-3757: Attachment: phase_test.patch Modified the testcase patch as per dims comments to add an fail

[jira] Commented: (AXIS2-3529) Axis2 server responds with Http 200 instead of 202 for the request of a dual channel invocation

[ https://issues.apache.org/jira/browse/AXIS2-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12576940#action_12576940 ] Ruwan Linton commented on AXIS2-3529: - Deepal, If the axis2 client receives the

[jira] Commented: (AXIS2-3529) Axis2 server responds with Http 200 instead of 202 for the request of a dual channel invocation

[ https://issues.apache.org/jira/browse/AXIS2-3529?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=12574841#action_12574841 ] Ruwan Linton commented on AXIS2-3529: - Dims, This causes some issues to Synapse,

[jira] Created: (AXIS2-1415) RESTClient.java sample client is out dated and the corresponding userguide as well

RESTClient.java sample client is out dated and the corresponding userguide as well -- Key: AXIS2-1415 URL: http://issues.apache.org/jira/browse/AXIS2-1415 Project:

[jira] Updated: (AXIS2-1415) RESTClient.java sample client is out dated and the corresponding userguide as well

[ http://issues.apache.org/jira/browse/AXIS2-1415?page=all ] Ruwan Linton updated AXIS2-1415: Attachment: rest_client.patch This patch contains the update to the RESTClient.java as well as the corresponding docs in the userguide, which were outdated

[jira] Created: (AXIS2-1395) Incorrect services.xml files are getting deployed without errors in axis2 without generating WSDL file

Incorrect services.xml files are getting deployed without errors in axis2 without generating WSDL file -- Key: AXIS2-1395 URL:

[jira] Updated: (AXIS2-1395) Incorrect services.xml files are getting deployed without errors in axis2 without generating WSDL file

[ http://issues.apache.org/jira/browse/AXIS2-1395?page=all ] Ruwan Linton updated AXIS2-1395: Attachment: services.xml This is the services.xml file which got deployed Incorrect services.xml files are getting deployed without errors in axis2 without

[jira] Created: (AXIS2-1398) Axis2 Crashed with a faulty service

Axis2 Crashed with a faulty service --- Key: AXIS2-1398 URL: http://issues.apache.org/jira/browse/AXIS2-1398 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: deployment Affects

[jira] Updated: (AXIS2-1398) Axis2 Crashed with a faulty service

[ http://issues.apache.org/jira/browse/AXIS2-1398?page=all ] Ruwan Linton updated AXIS2-1398: Attachment: services.xml Axis2 Crashed with a faulty service --- Key: AXIS2-1398 URL:

[jira] Commented: (AXIS2-1410) Axis2 sends SOAPFaults as a (SOAP message) when we are doing REST

[ http://issues.apache.org/jira/browse/AXIS2-1410?page=comments#action_12442778 ] Ruwan Linton commented on AXIS2-1410: - It is ok now. Thanks for the quick fix. Can U please close this jira Axis2 sends SOAPFaults as a (SOAP message)

[jira] Created: (AXIS2-1349) RPCMessageReceiver misbehaviour

RPCMessageReceiver misbehaviour --- Key: AXIS2-1349 URL: http://issues.apache.org/jira/browse/AXIS2-1349 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: rpc Affects Versions: 1.1

[jira] Commented: (AXIS2-1357) Samples are outdated in Axis2-1.1-RC1

[ http://issues.apache.org/jira/browse/AXIS2-1357?page=comments#action_12441894 ] Ruwan Linton commented on AXIS2-1357: - Error message which are going to users are non descriptive they should explain what the error is in simple terms,

[jira] Created: (AXIS2-1363) RPCInOutAsyncMessageReceiver mis behaviour

RPCInOutAsyncMessageReceiver mis behaviour -- Key: AXIS2-1363 URL: http://issues.apache.org/jira/browse/AXIS2-1363 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: core

[jira] Commented: (AXIS2-1357) Samples are outdated in Axis2-1.1-RC1

[ http://issues.apache.org/jira/browse/AXIS2-1357?page=comments#action_12441918 ] Ruwan Linton commented on AXIS2-1357: - yes sample is correct the problem is with RPCInOutAsyncMR, this issue is

[jira] Created: (AXIS2-1343) WSDL generation misbehaviour

WSDL generation misbehaviour Key: AXIS2-1343 URL: http://issues.apache.org/jira/browse/AXIS2-1343 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: core Affects Versions: 1.1

[jira] Updated: (AXIS2-1343) WSDL generation misbehaviour

[ http://issues.apache.org/jira/browse/AXIS2-1343?page=all ] Ruwan Linton updated AXIS2-1343: Attachment: services.xml WSDL generation misbehaviour Key: AXIS2-1343 URL:

[jira] Commented: (AXIS2-1343) WSDL generation misbehaviour

[ http://issues.apache.org/jira/browse/AXIS2-1343?page=comments#action_12441442 ] Ruwan Linton commented on AXIS2-1343: - I was using the deployement of aixs-admin in tomcat servlet container. WSDL generation misbehaviour