You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@fineract.apache.org by "James Dailey (Jira)" <ji...@apache.org> on 2022/11/11 01:14:00 UTC
[jira] [Commented] (FINERACT-1798) Extension point: command processing service
[ https://issues.apache.org/jira/browse/FINERACT-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632007#comment-17632007 ]
James Dailey commented on FINERACT-1798:
----------------------------------------
Aleks - When implementing this, please ensure we are looking at security aspects - additional command processing suggests to me a new potential route for attack. At a very high level commands should have isolated capability.
Workflow enhancements within the application seem like a nice to have. Would it make more sense to have this external to the application?
> Extension point: command processing service
> -------------------------------------------
>
> Key: FINERACT-1798
> URL: https://issues.apache.org/jira/browse/FINERACT-1798
> Project: Apache Fineract
> Issue Type: Improvement
> Reporter: Aleksandar Vidakovic
> Assignee: Aleksandar Vidakovic
> Priority: Major
> Fix For: 1.9.0
>
>
> Make the current - synchronous - command processing service replaceable. Provide an example implementation in custom modules based on Apache Camel + LMAX disruptor routes. Provide enough documentation to enable users to implement their own command processing (could by a way to integrate workflow engines).
--
This message was sent by Atlassian Jira
(v8.20.10#820010)