Geek Answers Handbook

Standard conventions or good practices when assigning local / remote EJB interfaces?

Are there any conventions or good practices when naming interfaces for EJBs? I also try to apply some DDD principles in my application, so I use the “service” sterotype in classes, which are the interface for the outside world.

If I have an EJB QuestionService that provides business logic operations to clients, what would I call @ Local / @ Remote Interface? All the books I've read so far only call them QuestionServiceLocal / QuestionServiceRemote. Is this sufficient (I'm not trying to get a feel for names, but I wonder if there are more efficient naming conventions)?

Also, are there other / better ways of naming "services" in an application than just adding the suffix "... Service" in each class?

+5
source share
1 answer

Java naming conventions are created and accepted by the community as well as senior developers at the company.
Therefore, every time we run into naming problems, we can go ahead with the following:

  • If the project already exists, simply execute the coventions project name
  • If this is a new project that you are creating, do the following:
    a. QuestionServiceLocal/ QuestionServiceRemote- very good approach
    b. QuestionServicemore than enough to indicate service
+4
source

More articles:


All Articles