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 "Asankha C. Perera (JIRA)" <ji...@apache.org> on 2009/02/27 03:02:02 UTC

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

     [ https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Asankha C. Perera resolved AXIS2-2993.
--------------------------------------

    Resolution: Won't Fix
      Assignee: Asankha C. Perera  (was: Deepal Jayasinghe)

HTTP/S NIO is not within the Axis2 project anymore. If there is any issue, please use the latest version from Synapse

> 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.