[jira] Created: (AXIS2-1246) Generated SOAP Action header is invalid

2006-09-27 Thread Thomas Eckoldt (JIRA)
Generated SOAP Action header is invalid --- Key: AXIS2-1246 URL: http://issues.apache.org/jira/browse/AXIS2-1246 Project: Apache Axis 2.0 (Axis2) Issue Type: Bug Components: core Affects

[jira] Commented: (AXIS2-939) Client API does not remove OperationContext instances from configuration context after MEP completes

2006-09-18 Thread Thomas Eckoldt (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-939?page=comments#action_12435471 ] Thomas Eckoldt commented on AXIS2-939: -- Please re-open the issue (I don't seem to have the access-rights to do it), the problem still exists. The method call

[jira] Commented: (AXIS2-939) Client API does not remove OperationContext instances from configuration context after MEP completes

2006-08-09 Thread Thomas Eckoldt (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-939?page=comments#action_12426858 ] Thomas Eckoldt commented on AXIS2-939: -- Could you please re-open this issue until the bug in AddressingBasedDispatcher is fixed? Thanks! Client API does not

[jira] Commented: (AXIS2-939) Client API does not remove OperationContext instances from configuration context after MEP completes

2006-07-31 Thread Thomas Eckoldt (JIRA)
[ http://issues.apache.org/jira/browse/AXIS2-939?page=comments#action_12424541 ] Thomas Eckoldt commented on AXIS2-939: -- Fix in OutInAxisOperation works fine, but in AddressingBasedDispatcher the problem is not resolved. I think the

[jira] Created: (AXIS2-939) Client API does not remove OperationContext instances from configuration context after MEP completes

2006-07-28 Thread Thomas Eckoldt (JIRA)
Client API does not remove OperationContext instances from configuration context after MEP completes Key: AXIS2-939 URL: