[jira] Created: (AXIS2-3283) No access to the operationContextMap in the ConfigurationContext class

2007-10-18 Thread Alexander Koezle (JIRA)
No access to the operationContextMap in the ConfigurationContext class
--

 Key: AXIS2-3283
 URL: https://issues.apache.org/jira/browse/AXIS2-3283
 Project: Axis 2.0 (Axis2)
  Issue Type: Improvement
  Components: kernel
Affects Versions: 1.3
Reporter: Alexander Koezle


I'm upgrading my existing code based on axis 1.1 to the 1.3 version and I get a 
following problem: 

I used the ConfigurationContext#getOperationContextMap method to check if the 
map is empty or still has any registered operation contexts. I use that e.g. 
during the application shutdown to test, if some service calls are still 
running (e.g. if using non blocking calls). In 1.3 version the 
operationContextMap has only private access, so i can't check if it is empty or 
not.  So i would like to have something like isAnyOperationContextRegistered() 
method in the ConfigurationContext class. 

If there is another way to the information I need, please let me now.

regards

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]



[jira] Created: (AXIS2-3265) AxisCallback#onComplete is not called in OutInAxisOperation.NonBlockingInvocationWorker#run

2007-10-10 Thread Alexander Koezle (JIRA)
AxisCallback#onComplete is not called in 
OutInAxisOperation.NonBlockingInvocationWorker#run
---

 Key: AXIS2-3265
 URL: https://issues.apache.org/jira/browse/AXIS2-3265
 Project: Axis 2.0 (Axis2)
  Issue Type: Bug
  Components: kernel
Affects Versions: 1.3
Reporter: Alexander Koezle
Priority: Minor


Hi, 

I'm trying to refactor my existing code and replace deprecated Callback 
interface with the  new AxisCallback.  

I miss the call of AxisCallback#onComplete() while invoking of a non blocking 
service in OutInAxisOperation.NonBlockingInvocationWorker#run. I expect the 
onComplete call after the call of onMessage() or onFault() as it already done 
for Callback instance (setComplete()).

I mean these lines:

{code:}
public void run() {
try {
// send the request and wait for response
MessageContext response = send(msgctx);
// call the callback
if (response != null) {
SOAPEnvelope resenvelope = response.getEnvelope();
SOAPBody body = resenvelope.getBody();
if (body.hasFault()) {
// If a fault was found, create an AxisFault with a 
MessageContext so that
// other programming models can deserialize the fault 
to an alternative form.
AxisFault fault = new AxisFault(body.getFault(), 
response);
if (callback != null) {
callback.onError(fault);
} else {
axisCallback.onError(fault);
}

} else {
if (callback != null) {
AsyncResult asyncResult = new AsyncResult(response);
callback.onComplete(asyncResult);
} else {
axisCallback.onMessage(response);
}

}
}

} catch (Exception e) {
if (callback != null) {
callback.onError(e);
} else {
axisCallback.onError(e);
}

} finally {
if (callback != null) {
callback.setComplete(true);
}
}
}
{code}




-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.


-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]