[
https://issues.apache.org/jira/browse/OFBIZ-7415?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15401253#comment-15401253
]
Jacques Le Roux edited comment on OFBIZ-7415 at 7/31/16 5:30 PM:
-----------------------------------------------------------------
My opinion is that most of the time it's better to be DRY, and in some (rares)
cases not. It seems we are not in one of the rare cases.
So the idea would be to evaluate Pierre's solution and see if, like he claims
he did with his omultisafepay component, we can't provide a common
specialpurpose/payments component for 3rd party payment methods.
Based on Pierre's "omultisafepay" component ideas, and hopefully code, we would
create this common specialpurpose/payments component that would provide the
common basis and would be called by other sub-layer payment methods components.
So basically we would create 3rd party components (hopefully later plugins) for
each currently existing OOTB payment methods which would reuse what the common
specialpurpose/payments component would provide (an API interfaces hopefully).
Disclamer: I did not review Pierre's work, so this suggestion is only based on
what he said at http://markmail.org/message/3e337pta54xizvjv
This would create rock solid foundations for 3rd payment component/plugins
creation. Users would be able to use what exists OTTB (mostly destined for US)
and create component/plugins based on other payment solutions from everywhere
in the world.
According to Pierre, the same would apply to shipment solutions. It would be
great if Pierre would give us more details on his implementation.
was (Author: jacques.le.roux):
My opinion is that most of the time it's better to be DRY, and in some (rares)
cases not. It seems we are not in one of the rare cases.
So the idea would be to evaluate Pierre's solution and see if, like he claims
he did with his omultisafepay component, we can't provide a common
specialpurpose/payments component for 3rd party payment methods.
Based on Pierre's "omultisafepay" component ideas, and hopefully code, we would
create this common specialpurpose/payments component that would provide the
common basis and would be called by other sub-layer payment methods components.
So basically we would create 3rd party components (hopefully later plugins) for
each currently existing OOTB payment methods which would reuse what the common
specialpurpose/payments component would provide (an API interfaces hopefully).
Disclamer: I did not review Pierre's work, so this suggestion is only based on
what he said at http://markmail.org/message/3e337pta54xizvjv
This would create rock solid foundations for 3rd payment component/plugins
creation. Users would be able to use what exists OTTB (mostly destined for US)
and create component/plugins based on other payment solutions from everywhere
in the world.
According to Pierre, the same would apply to shipment solutions. It would be
great if Pierre would give us more details on his implemenation.
> Move 3rd party payment integrations from accounting application to
> sepcialpurpose
> ---------------------------------------------------------------------------------
>
> Key: OFBIZ-7415
> URL: https://issues.apache.org/jira/browse/OFBIZ-7415
> Project: OFBiz
> Issue Type: Improvement
> Components: accounting
> Affects Versions: Trunk
> Reporter: Pierre Smits
> Assignee: Mridul Pathak
>
> This is a placeholder issue to capture all sub tasks for removing 3rd party
> payment integrations from accounting application and moving to a new
> component in special purpose.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
