You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by "Imesh Gunaratne (JIRA)" <ji...@apache.org> on 2013/11/05 13:49:19 UTC
[jira] [Updated] (STRATOS-163) Introduce a Message Processor Chain
Model and Extract Generic Functionality in Topology Event Message Delegator
[ https://issues.apache.org/jira/browse/STRATOS-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Imesh Gunaratne updated STRATOS-163:
------------------------------------
Summary: Introduce a Message Processor Chain Model and Extract Generic Functionality in Topology Event Message Delegator (was: Introduce an Message Processor Chain Model and Extract Generic Functionality in Topology Event Message Delegator)
> Introduce a Message Processor Chain Model and Extract Generic Functionality in Topology Event Message Delegator
> ---------------------------------------------------------------------------------------------------------------
>
> Key: STRATOS-163
> URL: https://issues.apache.org/jira/browse/STRATOS-163
> Project: Stratos
> Issue Type: Sub-task
> Reporter: Imesh Gunaratne
> Assignee: Imesh Gunaratne
> Fix For: 4.0.0 Alpha 1
>
>
> Currently the Topology Event Message Delegator is tightly coupled with its message processor chain and does not have a generic processor chain definition. The idea of this task is to extract out the common functionality and make it more generic so that it could be easily re-used by providing custom message processor chains.
--
This message was sent by Atlassian JIRA
(v6.1#6144)