I have an interface which contains 10 methods such as SendInvoice, SaveInvoiceAsDraft, SendInvoiceReceivedMail, DeleteInvoiceFromDrafts, CancelInvoice etc. I need to create 5 different concrete classes which will be implement these methods. 5 different class for 5 different vendors. So, every vendors have their own web services.
Some of these vendors don't have like CancelInvoice or some don't have DeleteInvoiceFromDrafts. I think I need to use interface segregation principle otherwise in some of concrete classes will thrown exceptions which can't provide implementation.
Should I create one interface for each one of methods?
How would you name these interfaces that contains only one method?
In case of using Command pattern I will need to use these concrete classes as Receiver. Do you have any suggestion, piece of code to show implementation of SOLID and Command Pattern or benefical link?
I think you did excellent job by creating this project and making implementation of each pattern in one place.
Basically my idea is to provide interactive UI for beginners as well as engineers already using patterns/antipatterns :)
So, something like this:
Don't want you misunderstand me, but when I see what is in the repo - I am scared of such a huge list :D
I study informatics at University of Szeged and me and my group mates (other 4 people) got a task
to contribute into java-design-patterns
I have a question for you. We are thinking about taking some issues from the github repo, and are there some kind of that you can recommend for us? We think that implementing a few patterns will be a good idea. Do you know some kind of pattern, which can be easier to understand and implement?
We would need fast response, because we would need to choice issues today.