What are some good package naming conventions for domain specific object models. For example, say you have a Person.java POJO, would you put it in a mydomain.model or mydomain.entity or mydomain.om (object model) package. The idea is to separate the MVC model objects from the domain object model. Our MVC based application has a model package that contains behavior but using that package to contain our domain object model seems inappropriate and potentially confusing.
What are some good package naming conventions for domain specific object models. For example,
Share
I use ‘com.mycompany.domain’ personally, but that might not be the best answer.