You are viewing a plain text version of this content. The canonical link for it is here.

Posted to java-dev@axis.apache.org by "Deepal Jayasinghe (JIRA)" <ji...@apache.org> on 2009/02/27 04:06:01 UTC

[jira] Commented: (AXIS2-2993) the async message receiver could use NIO

    [ https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677234#action_12677234 ] 

Deepal Jayasinghe commented on AXIS2-2993:
------------------------------------------

Hi Asankha,

I know the transport is not there in Axis2 anymore, but the solution should not be to use from synapse. We need to make the transport available somehow. 

Thank you!
Deepal

> the async message receiver could use NIO
> ----------------------------------------
>
>                 Key: AXIS2-2993
>                 URL: https://issues.apache.org/jira/browse/AXIS2-2993
>             Project: Axis 2.0 (Axis2)
>          Issue Type: Improvement
>          Components: kernel
>    Affects Versions: 1.2
>         Environment: all
>            Reporter: Michele Mazzucco
>            Assignee: Asankha C. Perera
>
> AbstractMessageReceiver does the job of deciding (based on the AbstractMessageReceiver.DO_ASYNC property) whether or not to spin up a thread to do the work of invokeBusinessLogic(MessageContext). What about using NIO instead?

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