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 "Michele Mazzucco (JIRA)" <ji...@apache.org> on 2007/07/20 15:10:06 UTC
[jira] Created: (AXIS2-2993) the async message receiver could use
NIO
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
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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Resolved: (AXIS2-2993) the async message receiver could use
NIO
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ 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.
[jira] Assigned: (AXIS2-2993) the async message receiver could use
NIO
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Deepal Jayasinghe reassigned AXIS2-2993:
----------------------------------------
Assignee: Deepal Jayasinghe
> 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: Deepal Jayasinghe
>
> 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.
---------------------------------------------------------------------
To unsubscribe, e-mail: axis-dev-unsubscribe@ws.apache.org
For additional commands, e-mail: axis-dev-help@ws.apache.org
[jira] Commented: (AXIS2-2993) the async message receiver could use
NIO
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677238#action_12677238 ]
Deepal Jayasinghe commented on AXIS2-2993:
------------------------------------------
sure :), we can not make Message receiver transport dependent.
> 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.
[jira] Commented: (AXIS2-2993) the async message receiver could use
NIO
Posted by "Asankha C. Perera (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/AXIS2-2993?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12677236#action_12677236 ]
Asankha C. Perera commented on AXIS2-2993:
------------------------------------------
Hi Deepal
Lets take this concrete case as an example, why would one want to invoke the business logic in another thread when the transports are built to inject messages with worker threads designed "to do the work". I think I should have marked this issue as invalid instead?
thanks
asankha
> 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.
[jira] Commented: (AXIS2-2993) the async message receiver could use
NIO
Posted by "Deepal Jayasinghe (JIRA)" <ji...@apache.org>.
[ 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.