[jira] Resolved: (AXIS2-4247) JAX-WS API fails to build an endpoint reference (IllegalStateException) when service is published with Endpoint.publish()

[ https://issues.apache.org/jira/browse/AXIS2-4247?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Nagy resolved AXIS2-4247. -- Resolution: Fixed Assignee: Bill Nagy JAX-WS API fails to build an endpoint reference

[jira] Resolved: (AXIS2-3547) JAXWS Sessions working in Standalone Axis2+Tomcat / Axis2+SimpleAxisServer with Simple JAXWS client

[ https://issues.apache.org/jira/browse/AXIS2-3547?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Nagy resolved AXIS2-3547. -- Resolution: Invalid I've tried out a number of scenarios, and a JAX-WS client and service are able to

[jira] Assigned: (AXIS2-2098) There are numerous public methods on MessageContext that do not have comments.

[ https://issues.apache.org/jira/browse/AXIS2-2098?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Nagy reassigned AXIS2-2098: Assignee: Roy A. Wood Jr. (was: Bill Nagy) There are numerous public methods on MessageContext

[jira] Assigned: (AXIS2-2095) There are numerous public methods on ConfigurationContext which do not have comments.

[ https://issues.apache.org/jira/browse/AXIS2-2095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Nagy reassigned AXIS2-2095: Assignee: Roy A. Wood Jr. (was: Bill Nagy) There are numerous public methods on

[jira] Resolved: (AXIS2-2084) Improve performance in AxisEngine by removing calls to MessageContext.activate()

[ https://issues.apache.org/jira/browse/AXIS2-2084?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Nagy resolved AXIS2-2084. -- Resolution: Fixed Assignee: Bill Nagy Improve performance in AxisEngine by removing calls to

[jira] Resolved: (AXIS2-2002) Reduce the trace messages for object serialization to improve performance with trace enabled

[ https://issues.apache.org/jira/browse/AXIS2-2002?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Nagy resolved AXIS2-2002. -- Resolution: Fixed Reduce the trace messages for object serialization to improve performance with

[jira] Created: (AXIS2-2094) The class level comment on ConfigurationContext is not very descriptive.

The class level comment on ConfigurationContext is not very descriptive. Key: AXIS2-2094 URL: https://issues.apache.org/jira/browse/AXIS2-2094 Project: Axis 2.0 (Axis2)

[jira] Created: (AXIS2-2095) There are numerous public methods on ConfigurationContext which do not have comments.

There are numerous public methods on ConfigurationContext which do not have comments. - Key: AXIS2-2095 URL: https://issues.apache.org/jira/browse/AXIS2-2095

[jira] Created: (AXIS2-2096) The isServerSide/setServerSide methods on MessageContext are inappropriately named.

The isServerSide/setServerSide methods on MessageContext are inappropriately named. --- Key: AXIS2-2096 URL: https://issues.apache.org/jira/browse/AXIS2-2096 Project:

[jira] Created: (AXIS2-2097) The class level comment on MessageContext is not very descriptive.

The class level comment on MessageContext is not very descriptive. -- Key: AXIS2-2097 URL: https://issues.apache.org/jira/browse/AXIS2-2097 Project: Axis 2.0 (Axis2) Issue

[jira] Created: (AXIS2-2098) There are numerous public methods on MessageContext that do not have comments.

There are numerous public methods on MessageContext that do not have comments. -- Key: AXIS2-2098 URL: https://issues.apache.org/jira/browse/AXIS2-2098 Project: Axis 2.0

[jira] Created: (AXIS2-2099) The class level comment on PhaseHolder is not very descriptive.

The class level comment on PhaseHolder is not very descriptive. --- Key: AXIS2-2099 URL: https://issues.apache.org/jira/browse/AXIS2-2099 Project: Axis 2.0 (Axis2) Issue Type: Task

[jira] Created: (AXIS2-2100) The class level comment on PhaseResolver is not very descriptive.

The class level comment on PhaseResolver is not very descriptive. - Key: AXIS2-2100 URL: https://issues.apache.org/jira/browse/AXIS2-2100 Project: Axis 2.0 (Axis2) Issue Type:

[jira] Created: (AXIS2-2101) The engageModuleToOperation method on PhaseResolver is missing a comment.

The engageModuleToOperation method on PhaseResolver is missing a comment. - Key: AXIS2-2101 URL: https://issues.apache.org/jira/browse/AXIS2-2101 Project: Axis 2.0 (Axis2)

[jira] Created: (AXIS2-2102) The logic in the engageModuleToOperation method on PhaseResolver is very obfuscated.

The logic in the engageModuleToOperation method on PhaseResolver is very obfuscated. Key: AXIS2-2102 URL: https://issues.apache.org/jira/browse/AXIS2-2102 Project:

[jira] Resolved: (AXIS2-2076) Improve trace correlation for message context serialization

[ https://issues.apache.org/jira/browse/AXIS2-2076?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Bill Nagy resolved AXIS2-2076. -- Resolution: Fixed Assignee: Bill Nagy Improve trace correlation for message context

[jira] Created: (AXIS2-1649) Invocation with useSeparateListener option set will never complete if an error occurs in the outbound transport

Invocation with useSeparateListener option set will never complete if an error occurs in the outbound transport --- Key: AXIS2-1649 URL:

[jira] Closed: (AXIS2-1233) Handlers do not get a chance to undo work if a fault occurs or complete work when message processing finishes (this was split off from AXIS2-653)

[ http://issues.apache.org/jira/browse/AXIS2-1233?page=all ] Bill Nagy closed AXIS2-1233. Resolution: Fixed Handlers do not get a chance to undo work if a fault occurs or complete work when message processing finishes (this was split off from AXIS2-653)

[jira] Closed: (AXIS2-1238) org.apache.axis2.deployment.util.PhasesInfo has hard coded phase names which prevent the phase ordering in axis2.xml from functioning properly

[ http://issues.apache.org/jira/browse/AXIS2-1238?page=all ] Bill Nagy closed AXIS2-1238. Resolution: Invalid This was addressed (at least partially -- there are still hardcoded names, but less of them) between the time that I brought it up and when I

[jira] Reopened: (AXIS2-1233) Handlers do not get a chance to undo work if a fault occurs or complete work when message processing finishes (this was split off from AXIS2-653)

[ http://issues.apache.org/jira/browse/AXIS2-1233?page=all ] Bill Nagy reopened AXIS2-1233: -- This issue is being reopened as the changes were backed out due to Sanjiva's -1. Handlers do not get a chance to undo work if a fault occurs or complete

[jira] Created: (AXIS2-1233) Handlers do not get a chance to undo work if a fault occurs or complete work when message processing finishes (this was split off from AXIS2-653)

Handlers do not get a chance to undo work if a fault occurs or complete work when message processing finishes (this was split off from AXIS2-653) -

[jira] Updated: (AXIS2-1233) Handlers do not get a chance to undo work if a fault occurs or complete work when message processing finishes (this was split off from AXIS2-653)

[ http://issues.apache.org/jira/browse/AXIS2-1233?page=all ] Bill Nagy updated AXIS2-1233: - Attachment: qoslifecyclepatch.txt This is the patch that was originally attached to AXIS2-653. Handlers do not get a chance to undo work if a fault occurs or

[jira] Updated: (AXIS2-653) Handler method cleanup is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=all ] Bill Nagy updated AXIS2-653: Attachment: (was: qoslifecyclepatch.txt) Handler method cleanup is never called Key: AXIS2-653

[jira] Commented: (AXIS2-653) Handler method cleanup is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=comments#action_12437571 ] Bill Nagy commented on AXIS2-653: - I've created a new task, AXIS2-1233, to track the handler invocation/lifecycle issues (i.e. not the cleanup(...)) and moved my

[jira] Created: (AXIS2-1237) OutInAxisOperation invokes the InFlow and InFaultFlow when a fault is received in a response

OutInAxisOperation invokes the InFlow and InFaultFlow when a fault is received in a response Key: AXIS2-1237 URL: http://issues.apache.org/jira/browse/AXIS2-1237

[jira] Created: (AXIS2-1238) org.apache.axis2.deployment.util.PhasesInfo has hard coded phase names which prevent the phase ordering in axis2.xml from functioning properly

org.apache.axis2.deployment.util.PhasesInfo has hard coded phase names which prevent the phase ordering in axis2.xml from functioning properly --

[jira] Updated: (AXIS2-653) Handler method cleanup is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=all ] Bill Nagy updated AXIS2-653: Attachment: qoslifecyclepatch.txt Here's a patch that implements the QoS/handler lifecycle. (This still doesn't fix the module lifecycle issue [i.e. the cleanup()

[jira] Updated: (AXIS2-1119) Dispatcher support for ServiceMode=MESSAGE annotation

[ http://issues.apache.org/jira/browse/AXIS2-1119?page=all ] Bill Nagy updated AXIS2-1119: - Component/s: jaxws Dispatcher support for ServiceMode=MESSAGE annotation - Key: AXIS2-1119

[jira] Commented: (AXIS2-653) Handler method cleanup is never called

[ http://issues.apache.org/jira/browse/AXIS2-653?page=comments#action_12431888 ] Bill Nagy commented on AXIS2-653: - Hi Deepal. I actually proposed this modification to the lifecycle sometime in April (

[jira] Created: (AXIS2-1095) Transmission with MTOM enabled fails when client sets useSeparateListener for req/rsp

Transmission with MTOM enabled fails when client sets useSeparateListener for req/rsp - Key: AXIS2-1095 URL: http://issues.apache.org/jira/browse/AXIS2-1095 Project:

[jira] Updated: (AXIS2-1095) Transmission with MTOM enabled fails when client sets useSeparateListener for req/rsp

[ http://issues.apache.org/jira/browse/AXIS2-1095?page=all ] Bill Nagy updated AXIS2-1095: - Attachment: MTOM-enabled-axis2.xml Transmission with MTOM enabled fails when client sets useSeparateListener for req/rsp

[jira] Updated: (AXIS2-1095) Transmission with MTOM enabled fails when client sets useSeparateListener for req/rsp

[ http://issues.apache.org/jira/browse/AXIS2-1095?page=all ] Bill Nagy updated AXIS2-1095: - Affects Version/s: (was: M2) Transmission with MTOM enabled fails when client sets useSeparateListener for req/rsp

[jira] Updated: (AXIS2-1095) Reception of response from server when using MTOM fails when client sets useSeparateListener for req/rsp

[ http://issues.apache.org/jira/browse/AXIS2-1095?page=all ] Bill Nagy updated AXIS2-1095: - Summary: Reception of response from server when using MTOM fails when client sets useSeparateListener for req/rsp (was: Transmission with MTOM enabled fails when

[jira] Commented: (AXIS2-938) Plugpoint to allow for migration between context and TLS

[ http://issues.apache.org/jira/browse/AXIS2-938?page=comments#action_12424587 ] Bill Nagy commented on AXIS2-938: - (Sorry that I'm a little late to the discussion; I just switched machines and apparently my mail filtering is screwed up.) The

[jira] Resolved: (AXIS2-910) JAXWS: Update AxisInvocationController to use the OperationClient instead of the ServiceClient

[ http://issues.apache.org/jira/browse/AXIS2-910?page=all ] Bill Nagy resolved AXIS2-910. - Resolution: Fixed JAXWS: Update AxisInvocationController to use the OperationClient instead of the ServiceClient

[jira] Created: (AXIS2-938) Plugpoint to allow for migration between context and TLS

Plugpoint to allow for migration between context and TLS Key: AXIS2-938 URL: http://issues.apache.org/jira/browse/AXIS2-938 Project: Apache Axis 2.0 (Axis2) Issue Type: New Feature

[jira] Updated: (AXIS2-938) Plugpoint to allow for migration between context and TLS

[ http://issues.apache.org/jira/browse/AXIS2-938?page=all ] Bill Nagy updated AXIS2-938: Attachment: tlsmigrator.patch Plugpoint to allow for migration between context and TLS Key:

[jira] Assigned: (AXIS2-910) JAXWS: Update AxisInvocationController to use the OperationClient instead of the ServiceClient

[ http://issues.apache.org/jira/browse/AXIS2-910?page=all ] Bill Nagy reassigned AXIS2-910: --- Assignee: Bill Nagy (was: Rich Scheuerle) JAXWS: Update AxisInvocationController to use the OperationClient instead of the ServiceClient

[jira] Resolved: (AXIS2-909) JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in AxisInvocationController.

[ http://issues.apache.org/jira/browse/AXIS2-909?page=all ] Bill Nagy resolved AXIS2-909. - Resolution: Fixed JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in AxisInvocationController.

[jira] Assigned: (AXIS2-909) JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in AxisInvocationController.

[ http://issues.apache.org/jira/browse/AXIS2-909?page=all ] Bill Nagy reassigned AXIS2-909: --- Assignee: Bill Nagy JAXWS: Fix the invokeOneWay and invokeAsync (callback) implementations in AxisInvocationController.