关于Java接口命名，存在不同的观点。一种是在接口名前加'I'，如IDocumentMappingService，另一种是在实现类名后加'Impl'。然而，一些开发者认为这两种方式都不理想，主张接口名称应明确其契约，实现类则说明如何实现契约。文章讨论了通用的接口命名，如EmployeeRepository implements Repository，或使用'Default'或'Support'作为实现类前缀，例如DefaultEmployeeRepository。最后指出，重要的是保持命名一致性，并提供了一些具体的命名建议。
I work on a Java web-app that uses Spring for dependency injection and JMock for mocking out these dependencies in our unit tests.
Currently our team is at a point were we have a few different opinions in terms of how to name certain interfaces that we use. We have no issue with naming the interfaces in our domain that have multiple implementations, that is simple. However, when it comes to interfaces for which we only have one implementation and intend on only having one implementation in the future, we have hit a snag.
The reason that we have such interfaces is purely for mocking, for example, we have services and repositories that we mock out in our unit tests and these services will be named "DocumentMappingService" or for repositories "EmployeeRepository". At the moment some of the guys just prefix the associated interface name with an "I", i.e. "IDocument
最低0.47元/天 解锁文章
1628
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
