Ask questions and see you at November, 5th, 6.PM. CET: http://www.ustream.tv/channel/adambien
Also checkout recent episode:
Please keep the questions Java EE-stic. Means: as short and as concise as only possible.
Last active
November 5, 2018 16:40
-
-
Save AdamBien/4a3ad4c69c1ccfd0d3b3e02a21adfefb to your computer and use it in GitHub Desktop.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Hi Adam,
I have a short question for the BCE-structuring with multiple implementations of a given "domain-aspect". Given the case, there is a payment-feature in an application. And the payment can be performed via different payment-providers.
So, basically, I would have:
/business/payment/ [b/c/e] but inside, I will have PaymentProviderA, PaymentProviderB and so on. All payment-provider should behave the same, so there is an "AbstractPaymentController", so that the concrete PaymentControllers only need to implement there specific API-implementation of the specific PaymentProvider.
Would it be correct to structure the packages as following, or do you have a better idea:
.../business/payment/boundary/PaymentResource.class
.../business/payment/control/AbstractPaymentController.class
.../business/payment/PaymentProviderA/control/PPAController.class
.../business/payment/PaymentProviderB/control/PPBController.class
Thank you very much in advance from Hamburg
Ulrich