You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@ofbiz.apache.org by "Adrian Crum (JIRA)" <ji...@apache.org> on 2014/09/01 09:41:20 UTC

[jira] [Updated] (OFBIZ-5743) Clean Up and Organize Service Engine Classes

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

Adrian Crum updated OFBIZ-5743:
-------------------------------
    Attachment: OFBIZ-5743.patch

Patch is attached.

> Clean Up and Organize Service Engine Classes
> --------------------------------------------
>
>                 Key: OFBIZ-5743
>                 URL: https://issues.apache.org/jira/browse/OFBIZ-5743
>             Project: OFBiz
>          Issue Type: Improvement
>          Components: framework
>            Reporter: Adrian Crum
>            Priority: Minor
>         Attachments: OFBIZ-5743.patch
>
>
> Currently, the service engine classes are a bit muddled. GenericDispatcher (the default LocalDispatcher implementation) and DispatchContext have feature envy. Some functionality in DispatchContext belongs in ServiceDispatcher.
> I would like to clean this up a bit and provide better separation of concerns. The service engine API will not change - the work will be done "under the hood."
> My hope is to get the code to a point where DispatchContext becomes less integral to its neighbors, and it becomes more of a single-use lightweight container. Again, this will not change the API at all. 



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)