[
https://issues.apache.org/jira/browse/FINERACT-1798?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17632246#comment-17632246
]
Aleksandar Vidakovic commented on FINERACT-1798:
------------------------------------------------
[~jdailey] any contribution here would not even be part of our official
distribution (read: this would be developed in the custom module folder next to
the other example modules; just to show enough how this could look like)... so,
yes, all your concerns are valid... but it's sample code, it will not be
deployed with the default Fineract distribution; of course we would add
additionally a clear disclaimer "here be dragons" for people who start to
replace that part of the system... still, I see demand for something like this
especially because of the "Synchronous" prefix in the name of the current
implementation. And maybe a community member puts some effort into an
alternative implementation (including kicking the tires in production and
testing)... and contributes it back to upstream.
> 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)
